Firefox freezed for a second or two and they i get a confirm dialog asking me if I want to abort the script that is causing this freeze.
it might take longer on some systems, but Mozilla will detect a loop asking if you want to abort the script. In some cases this will take a minute or two. Please let us know if that does not happen.
QA Contact: mconnor
four minutes is longer than in should take, it took about 10-15 seconds here, dunno what's different on your build. What about an official nightly? (not a CVS pull with custom options) If you can suggest a way of predicting code that will loop endlessly before it even gets executing, I'm sure it would be nice to have. btw, if you open Privacy under Options, does your build crash? try it and I'll tell you why later :)
no, opening the privacy options doesn't crash my build (i tried expanding and collapising all the options). the thing is... i don't understand why it would be 1-2 seconds on one computer, and 10-15 on someone elses, and more on mine. i don't think the prediction code should be allowed to make you wait with an unusable browser for an unpredictable amount of time. i believe the user should always have control to abort an action at their will and not after the browser decides that it is ready to abort the action. basically all you would need to do is check to see if the user pressed stop or esc, and if that happens, stop executing code. unfortunately, the browser is too "locked up" to respond to anything. i guess i have to debate now whether this turns this bug report into a enhancement request or if it still is a problem for some people... sorry, i'm not really in the mood to try another build now so we'll just have to leave it as it is. thanks for the prompt replies.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → WORKSFORME
This looks like a true bill, Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a) Gecko/20040417 Firefox/0.8.0+ Something like 13 minutes before the cancel dialog Ben
that's really bizarre timing. I wonder what's different about your builds than everyone I had test? In any case, other than continued work on the logic, this isn't going to get any better without fixing the "JS executes in the UI thread" bug. Feel free to fix that, if you have a few months to spare :(
You need to log in before you can comment on or make changes to this bug.