Closed
Bug 305701
Opened 19 years ago
Closed 19 years ago
[@ 0xffffff4d]
Categories
(Core :: DOM: Core & HTML, defect, P5)
Tracking
()
RESOLVED
DUPLICATE
of bug 314484
People
(Reporter: timeless, Unassigned)
Details
(Keywords: crash)
Crash Data
reproducable: didn't try. the build was so unusable (i couldn't get chatzilla to open w/o an error dialog) that i was quiting in an effort to run an older build that worked (minus the fact that bookmark keywords didn't work...). probably a dupe of bug 297366 or bug 301065 the skid marks are at least a bit unusual. Incident ID: 8656610 Stack Signature 0xffffff4d 7455c044 Product ID FirefoxTrunk Build ID 2005082308 Trigger Time 2005-08-23 17:53:06.0 Platform Win32 Operating System Windows NT 5.1 build 2600 Module URL visited quiting User Comments Since Last Crash 385 sec Total Uptime 385 sec Trigger Reason Access violation Source File, Line No. N/A Stack Trace 0xffffff4d 0x01001008 js_GC [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/js/src/jsgc.c, line 1814] js_ForceGC [c:/builds/tinderbox/Fx- Trunk/WINNT_5.2_Depend/mozilla/js/src/jsgc.c, line 1510] nsObserverService::NotifyObservers [c:/builds/tinderbox/Fx- Trunk/WINNT_5.2_Depend/mozilla/xpcom/ds/nsObserverService.cpp, line 235] NS_ShutdownXPCOM_P [c:/builds/tinderbox/Fx- Trunk/WINNT_5.2_Depend/mozilla/xpcom/build/nsXPComInit.cpp, line 776] ScopedXPCOMStartup::~ScopedXPCOMStartup [c:/builds/tinderbox/Fx- Trunk/WINNT_5.2_Depend/mozilla/toolkit/xre/nsAppRunner.cpp, line 547] main [c:/builds/tinderbox/Fx- Trunk/WINNT_5.2_Depend/mozilla/browser/app/nsBrowserApp.cpp, line 61] kernel32.dll + 0x16d4f (0x7c816d4f)
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P5
Comment 1•19 years ago
|
||
*** This bug has been marked as a duplicate of 314484 ***
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
i'm not sure this is a perfect match to that bug, but i don't really care either.
Updated•13 years ago
|
Crash Signature: [@ 0xffffff4d]
Updated•5 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•