Closed Bug 785038 Opened 13 years ago Closed 13 years ago

WebWorker crashes Firefox 14.0.1 (Ubuntu 10.04, Firebug 1.10.2)

Categories

(Core :: JavaScript Engine, defect)

14 Branch
x86_64
Linux
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 775543

People

(Reporter: info, Unassigned)

References

()

Details

My System: - Ubuntu 10.04 - 64 bit - Firefox 14.0.1 - Firebug 1.10.2 (empty profile with Firebug) Try this minimal working example, with the options shown (sorry, I am somehow not able to switch to the english version) in the screenshot: http://www.dennis-boldt.de/firebug-bug/ http://paste.dennis-boldt.de/2012/mozilla/firebug-bug.png Firefox crashes as soon I am clicking on the test-link. Impotant is the breakpoint. Without it, it is not crashing. Here the crash report: http://paste.dennis-boldt.de/2012/mozilla/firebug-bug
Or even just the crash id from about:crashes, assuming this is a mozilla.org Firefox build?
No, that's perfect. Looks like a null-deref when the Xray code touches the worker. This was actually fixed just yesterday in development builds; we're going to get a fix into Firefox 16 as well, but Firefox 15 will ship without that fix, unfortunately.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
And Dennis, thank you very much for the bug report!
Just in FF16? Means, I must downgrade or debug my Worker with Chrome. It's a pity. P.S.: it took quite a lot of time to figure it out :)
Unfortunately, yes. Code freeze for Firefox 15 was day before yesterday. :(
Target Milestone: mozilla15 → ---
You can use Aurora 16.0, http://www.mozilla.org/firefox/aurora/, or soon Firefox 16.0 Beta, http://www.mozilla.org/firefox/beta/.
Good idea. Thanks for the hint.
FYI: in Aurora 16.0a2 (2012-08-23), this bug is still existing.
The crash report for Aurora 16.0a2 (2012-08-23): bp-76e717b9-7bb0-4ae5-9a66-369742120824
(In reply to Dennis Boldt from comment #10) > FYI: in Aurora 16.0a2 (2012-08-23), this bug is still existing. Yes because the patch hasn't yet landed in Aurora. Se bug 775543 for more.
The bug is not existing in `Aurora 17.0a2 (2012-09-06)` anymore. Thanks for the fix.
You need to log in before you can comment on or make changes to this bug.