Closed Bug 308645 Opened 19 years ago Closed 19 years ago

Crash [@ _PR_MD_ATOMIC_DECREMENT - js_GC]

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: bugs.caleb, Unassigned)

Details

(Keywords: crash, regression, topcrash+)

Crash Data

I can't really find a way to reproduce this crash, but it's been hitting me for quite a while now, and it worked its way up to to the topcrashes list (No. 1). Bug 304367's stack looks similar, but i'm not 100% sure whether it's the same. A recent talkback ID: TB9369269X (Most of the stacks look exactly like this). ---------------- _PR_MD_ATOMIC_DECREMENT [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/nsprpub/pr/src/md/windows/ntmisc.c, line 733] js_GC [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/js/src/jsgc.c, line 1851] js_GC [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/js/src/jsgc.c, line 1564] ScopedXPCOMStartup::~ScopedXPCOMStartup [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/toolkit/xre/nsAppRunner.cpp, line 550] main [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/browser/app/nsBrowserApp.cpp, line 61] kernel32.dll + 0x16d4f (0x7c816d4f)
Severity: normal → critical
Flags: blocking1.9a1?
Another Talkback ID: TB9372435Z _PR_MD_ATOMIC_DECREMENT [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/nsprpub/pr/src/md/windows/ntmisc.c, line 733] js_GC [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/js/src/jsgc.c, line 1851] js_GC [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/js/src/jsgc.c, line 1564] nsAppStartup::Quit [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/toolkit/components/startup/src/nsAppStartup.cpp, line 204] main [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/browser/app/nsBrowserApp.cpp, line 61] kernel32.dll + 0x16d4f (0x7c816d4f)
Some more talkbacks: TB9354950Z TB9376664E
Summary: Crash [@ _PR_MD_ATOMIC_DECREMENT] → Crash [@ _PR_MD_ATOMIC_DECREMENT - js_GC]
Keywords: crash
I'd say "topcrash" instead of "topcrash+" as the crasher is not reproducible yet, and no "regression" unless we're sure this crash hasn't been there before.
This is probably in the wrong component, but if it really _is_ Firefox-only you might want to cc some Firefox folks to take a look...
Looks like this bug was resolved by some other bug... It's gone from the topcrashers table. -> WFM.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
This might have been resurrected as bug 347054.
Flags: blocking1.9a1?
Crash Signature: [@ _PR_MD_ATOMIC_DECREMENT - js_GC]
You need to log in before you can comment on or make changes to this bug.