Closed Bug 443340 Opened 18 years ago Closed 18 years ago

Crash in xul.dll, might be js3250!js_GC+0x2a5 [e:\fx19rel\winnt_5.2_depend\mozilla\js\src\jsgc.c @ 3239]

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
critical

Tracking

()

VERIFIED DUPLICATE of bug 427718

People

(Reporter: tmptgr, Unassigned)

References

Details

Attachments

(3 files)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; nl; rv:1.9) Gecko/2008052906 Firefox/3.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; nl; rv:1.9) Gecko/2008052906 Firefox/3.0 I was autoscrolling one of the 100+ tabs in 10 windows while listening to Gorky's Zygotic Minci (Sweet Johnny) on beta.last.fm, when suddenly WinDbg 6.9 caught an error (that might've been caught by Breakpad were it not for bug 422308). The expected errors are from the Flash plugin, but this one was serious. Reproducible: Sometimes Steps to Reproduce: 1. Load lots of tabs (Session Manager, should use built-in code.) 2. Surf for days, hibernating at night. 3. ??? Actual Results: Crash in xul.dll while scrolling with autoscroll (not sure if related). Expected Results: Keep on rolling. Current extensions: Add Bookmark Here 0.5.8 [DISABLED] Clean And Close 2.0 [DISABLED] FAYT 2.0.4 Firebug 1.2.0b4 Firefox Showcase 0.9.4.8 Flashblock 1.5.6 Nightly Tester Tools 2.0.2 Secure Login 0.9.2.4 Session Manager 0.6.1.13 United States English Dictionary 3.0.3 ViewSourceWith 0.2 I think none of those should crash Firefox.
Attached file annotated WinDbg log —
I closed some other programs after it said it didn't have enough memory for the stacktrace.
I have a system variable named _NT_SYMBOL_PATH set to SRV*c:\localsymbols\*http://symbols.mozilla.org/firefox C:\localsymbols contains a lot of folders with pdb files. So WinDbg couldn't find the symbols for my Firefox version (RC2 according to http://wiki.mozilla.org/QA/Firefox3/TestResults/RC2), not even on the symbol server, and i should uninstall RC2 and install 3.0 gold?
!sym noisy .reload /f
Attached file New crash trace. —
Thanks for the help! Should i do that every time i get a second chance exception? After waking up this machine, and finding it found an update, it appears i ran into bug 427718. Is there anything else i should do?
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: