Closed Bug 1038807 Opened 12 years ago Closed 8 years ago

crash in js::gc::IsAboutToBeFinalized<js::ScopeObject>

Categories

(Core :: JavaScript: GC, defect)

All
Windows NT
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 1081769

People

(Reporter: wsmwk, Unassigned)

Details

(Keywords: crash, regression)

Crash Data

work PC 64bit windows build Version 33.0a1 Build ID 20140707030202 It was up for ~4 days - so, two days unattended on the weekend, and 1.5 working days. This morning getting slower and slower Total Virtual Memory 8796092891136 Available Virtual Memory 8790533394432 System Memory Use Percentage 84 Available Page File 7125381120 Available Physical Memory 1288908800 last I looked in taskmgr, working set memory size was about 3.8GB This bug was filed from the Socorro interface and is report bp-cc376b53-bc38-4fb9-87a0-2b4312140715. ============================================================= 0 mozjs.dll js::gc::IsAboutToBeFinalized<js::ScopeObject> js/src/gc/Marking.cpp 1 mozjs.dll JSCompartment::sweepCrossCompartmentWrappers() js/src/jscompartment.cpp 2 mozjs.dll JSCompartment::sweep(js::FreeOp *,bool) js/src/jscompartment.cpp 3 mozjs.dll js::gc::GCRuntime::beginSweepingZoneGroup() js/src/jsgc.cpp 4 mozjs.dll js::gc::GCRuntime::beginSweepPhase(bool) js/src/jsgc.cpp 5 mozjs.dll js::gc::GCRuntime::incrementalCollectSlice(__int64,JS::gcreason::Reason,js::JSGCInvocationKind) js/src/jsgc.cpp 6 mozjs.dll js::gc::GCRuntime::gcCycle(bool,__int64,js::JSGCInvocationKind,JS::gcreason::Reason) js/src/jsgc.cpp 7 mozjs.dll js::gc::GCRuntime::collect(bool,__int64,js::JSGCInvocationKind,JS::gcreason::Reason) js/src/jsgc.cpp 8 mozjs.dll JS::FinishIncrementalGC(JSRuntime *,JS::gcreason::Reason) js/src/jsfriendapi.cpp 9 xul.dll FireForgetSkippable dom/base/nsJSEnvironment.cpp 10 xul.dll CCTimerFired dom/base/nsJSEnvironment.cpp
again bp-365b2aa1-7cc6-4db7-9ce3-920f52140724 Total Virtual Memory 8796092891136 Available Virtual Memory 8792795746304 System Memory Use Percentage 69 And the crash between that and comment 0 .. js::NukeCrossCompartmentWrappers(JSContext*, js::CompartmentFilter const&, js::CompartmentFilter const&, js::NukeReferencesToWindow) bp-e84a645b-f89a-487d-877f-7c3f92140718
(In reply to Wayne Mery (:wsmwk) from comment #1) > again > bp-365b2aa1-7cc6-4db7-9ce3-920f52140724 > Total Virtual Memory 8796092891136 > Available Virtual Memory 8792795746304 > System Memory Use Percentage 69 I lied - bp-365b2aa1-7cc6-4db7-9ce3-920f52140724 is js::gc::IsAboutToBeFinalized<js::ArrayBufferViewObject>, does not match signature for this bug report, and has no bug report > And the crash between that and comment 0 .. > js::NukeCrossCompartmentWrappers(JSContext*, js::CompartmentFilter const&, > js::CompartmentFilter const&, js::NukeReferencesToWindow) > bp-e84a645b-f89a-487d-877f-7c3f92140718 I just got NukeCrossCompartmentWrappers again bp-6a3313d4-09c9-43e9-8e5f-80fae2140724 "I had cleaned up all but a couple tabs. I think down to one window. Then, just before crash I clicked to restore a session. crash". Version 33.0a1 Build ID 20140715030207 I've updated now to version 34.0a1 nightly - perhaps the crash will go away?
Crash Signature: [@ js::gc::IsAboutToBeFinalized<js::ScopeObject>] → [@ js::gc::IsAboutToBeFinalized<js::ScopeObject>] [@ js::gc::IsAboutToBeFinalized<T>]
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INACTIVE
I'm going to guess this was fixed a few months later in bug 1081769
Resolution: INACTIVE → DUPLICATE
You need to log in before you can comment on or make changes to this bug.