Why so many crashes / freezes / not respondings?

[gary]

I've been waiting for someone else to post a topic about this, maybe it's just me.

I've had the same crashing / freezing / not responding since the beginning of my upgrade to Webuilder 2010 (currently 10.2.0.121). Problem has occurred on 3 different Win XP computers.

Scenario:
Working on file with 1000 or more lines of PHP code.
Inserting and editing a new line prior to ending the line with a semicolon. It only happens when the line of code is incomplete with no ; terminating the line.
Webuilder freezes (eternal hour glass). Trying to click anything on Webuilder window results in "(Not Responding)" appearing in the title bar. In a test, I waited 24 hours, and Webuilder still was not responding.
Solution is a Windows Task Manager "end task". All work is lost.
It only seems to happen if it's been 30 minutes or more since the last save of the file - lol. (this is probably just my bad luck, and not a cause).

Below is a screenshot of the crash tonight. The red arrow shows where I was last typing (note, no semicolon termination on this new line I was inserting)...


I am hoping someone else had the same problem, or can duplicate this so Karlis will be willing to fix the bug.

Cheers,
-Gary.

[xtom]

I've worked on php files with 2000+ lines with no problem (I'm on win7). Actually I have had a rare freeze/crash now and then but I'm not sure if it was down to other programs running, memory etc. Maybe it's falling over on some particular piece of code in your file? Does it happen on all files you edit or just the one?

[notuo]

gary, I am also in W7 and no problem like this.

I suggest send an email to support and add the offending file with a link to this thread. Maybe they can replicate it in their facilities.

Also (if you can), post the file here for the people with XP to test it.

[gary]

I came up with a tiny piece of code that repeatedly crashes WebBuilder. Open this file, go to line 13, put the cursor just in front of the curly bracket, and type the word "return". Then click somewhere else on the screen (as if you were going to copy a variable to paste after "return". It crashes with 50% success/failure on my Win XP machine.

Here is a snapshot of the exact moment it crashes:


The peculiar thing is the file must be in my default web files folder (for me that's C:\public_html\). Webuilder does not crash if I open this file from my desktop. It seems if you pause before trying to move the mouse/cursor after typing "return", it's more likely to crash.

I wonder if Webuilder is doing an automatic syntax check, and getting into some kind of endless loop. Obviously, there is a syntax error in the code when it crashes.

Here is the zipped file: http://www.orientaloutpost.com/tools/crash.zip

-Gary.

[gary]

I can even copy this code, and paste it into a new document (new php script) and get it to crash:

[gary]

If only I could have gotten the semicolon on the end of this line before it crashed...



If the code is good (proper syntax, and terminated with a semicolon) there's no crashing. But as you write new code, it's not valid as you're typing it.

[Capricorn]

I couldn't reproduce the crash with RapidPHP 10.2.0.121 on Windows Vista. So maybe I'm lucky or it is just a problem with WeBuilder.

[notuo]

Same here, no problem at all.

Windows 7 WB 10.2.0.12.

You need someone with XP.

[MikeyB]

Same here, no problem at all.

Windows 7 WB 10.2.0.12.

You need someone with XP.

Hi, Windows XP here, just tried about 20 times and no crashes at all.
Both opening the gettit2.php file, and also pasting it into a new PHP document, fine every time.

[mapleleaf]

I've had the same crashing / freezing / not responding since the beginning of my upgrade to Webuilder 2010 (currently 10.2.0.121). Problem has occurred on 3 different Win XP computers.

I am sure that you have done some house cleaning after these crashes occur, right? what about defragmenting your disk BUT also your registry?
Have you done a boot-defrag?

XP, in fact NFTS, is highly fragmentory but I am sure you know this.

In fact, once a year I wipe my HDD, and re-install XP.

CCleaner is a good one to use and I use it daily.

However, TLI in regards to your XP system, amount of RAM installed, CPU.

Have you uninstalled WB, did housecleaning then re-install?

I'd bet that the issue lies on your system and not with XP, I could be wrong and I have been in the past but from my experience 85%+ of issues reported by users are issues/problems on their system.

I also like many other who have replied I also do not get a problem on either XP or Win7, therefore using logical deduction it may be your system either with the OS or a corrupted dll.

mapleleaf

[gary]

I kind of gave up on this problem. I save my work constantly, and almost get a twitch when I have not saved for more than 5 minutes.

Looking back, everyone who tried to replicate this crash problem did it on Win 7 (or Vista). This only happens on Win XP. I can replicate it on multiple Win XP machines.

Version 11.2.2.131 and most previous versions of WeBuilder will do this.

I've upgraded, uninstalled, reinstalled, defragged, etc.

No solution, but I figured something out...

If I go to Options > Preferences > Language Options > PHP
And, I uncheck the box next to "Automatic PHP function suggestions", the crashes stop.

This is so stupid, and I've lost so much work and time over so many years because of this. I spend hours trying every possible option setting combination. I should get my next upgrade free for figuring this out (hint hint).

[Aivars]

Gary, I'll give this to WeBuilder team and make sure they use XP to replicate the problem.

[william070707]

I too have the same kind of problem,So I uninstalled first and then reinstalled it and working fine for me

[gary]

Actually, turning off "Automatic PHP function suggestions" solved most crash problems. It still crashes occasionally the moment I type a comma. So I'll always save before typing a comma. I can't duplicate all the crash scenarios I posted before. Maybe things changed after upgrades.

However, if I type a comma instead of "return" in my one example, it crashes every time.

[MikeyB]

Looking back, everyone who tried to replicate this crash problem did it on Win 7 (or Vista). This only happens on Win XP. I can replicate it on multiple Win XP machines.

I did post back in March 2011 testing on XP and could not get it to crash.
Don't have XP any more, on Windows 7 so can't try again.