Closed Bug 832377 Opened 7 years ago Closed 7 years ago
CPU-intensive script freezes or even crashes Firefox
Please provide a testcase as an attachment and a stack trace or crash ID from about:crashes.
The freeze is "normal" while the script runs due to the single Process. I get 5000133.10464928 as result with Mozilla/5.0 (Windows NT 6.1; WOW64; rv:21.0) Gecko/20130118 Firefox/21.0 Build: 20130118193510 Do you have a crash ID from about:crashes ? mid-air: Scoobidiver: The provided testcase works, put it in the URL bar as example
Assignee: nobody → general
Product: Firefox → Core
Here is my crash report on Windows: bp-3c3a9eb0-0444-45f4-b156-51d5e2130118
Oh, right, the original problem is different, so let's just keep this about that. The crash is a very recent regression in Nightly, and unlikely to be related to the original problem.
No longer blocks: compartment-mismatch
Crash Signature: [@ js::CompartmentChecker::fail(JSCompartment*, JSCompartment*)]
Well, I would expect the rest of the browser (GUI, other tabs, page rendering...) not to freeze while there's a script running, so even if there's a CPU-hogging script running this doesn't mean Firefox stops working until it finishes or the slow script dialog is open, and I can still use Firefox while the function finishes.
a) A script can always freeze Firefox since it's single process. b) There is a slow script warning that should allow you to stop the script after some time. It's quite possible that this isn't triggered for JS entered in the URL bar because such scripts are running AFAIK with Chrome privileges. What is now your issue. a) or b)
1) Scripts entered via the url bar don't run with chrome privileges. 2) Even chrome-privileged scripts have a timeout on them. The operation callback should really be running in this case. If it's not, that's a JS engine bug.
(In reply to cousteau from comment #10) > My problem is (a): scripts shouldn't freeze Firefox but run on a separate > thread. First, as a user, you are not able to choose the right solution to a problem. Then, the multi-process management is a long-standing issue and was part of Electrolysis (https://wiki.mozilla.org/Electrolysis) that was stopped because it requires to rewrite entirely the code. As a consequence, no new Firefox or HTLM5 features would be integrated into Firefox during several years and many developers would have stopped working for Mozilla. There are two alternative on-going projects: https://wiki.mozilla.org/Performance/Snappy https://wiki.mozilla.org/Performance/MemShrink > About the crash on the beta, well, that's actually a bug and it will stay like that.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: electrolysis
You need to log in before you can comment on or make changes to this bug.