Closed Bug 785582 Opened 12 years ago Closed 12 years ago

Intermittent Assertion failure: (thing)->compartment()->isCollecting() in browser_dbg_bfcache.js

Categories

(Core :: JavaScript Engine, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: philor, Unassigned)

References

Details

(Keywords: intermittent-failure, Whiteboard: [js:t])

https://tbpl.mozilla.org/php/getParsedLog.php?id=14690031&tree=Mozilla-Inbound Rev3 WINNT 5.1 mozilla-inbound debug test mochitest-other on 2012-08-24 19:32:16 PDT for push 0e8f4d4d62fe slave: talos-r3-xp-007 TEST-INFO | chrome://mochitests/content/browser/browser/devtools/debugger/test/browser_dbg_bfcache.js | Going back. Assertion failure: (thing)->compartment()->isCollecting(), at e:/builds/moz2_slave/m-in-w32-dbg/build/js/src/gc/Marking.cpp:568 nsStringStats => mAllocCount: 3266159 => mReallocCount: 141760 => mFreeCount: 3237687 -- LEAKED 28472 !!! => mShareCount: 7249771 => mAdoptCount: 235951 => mAdoptFreeCount: 235947 -- LEAKED 4 !!! TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/devtools/debugger/test/browser_dbg_bfcache.js | Exited with code -2147483645 during test run INFO | automation.py | Application ran for: 0:25:01.203000 INFO | automation.py | Reading PID log: c:\docume~1\cltbld\locals~1\temp\tmp7hq-grpidlog ==> process 932 launched child process 3740 ==> process 932 launched child process 3576 INFO | automation.py | Checking for orphan process with PID: 3740 INFO | automation.py | Checking for orphan process with PID: 3576 Downloading symbols from: http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-inbound-win32-debug/1345854358/firefox-17.0a1.en-US.win32.crashreporter-symbols.zip PROCESS-CRASH | chrome://mochitests/content/browser/browser/devtools/debugger/test/browser_dbg_bfcache.js | application crashed (minidump found) Crash dump filename: c:\docume~1\cltbld\locals~1\temp\tmpsky8xc\minidumps\2cf2b397-9902-43f9-a03b-caa598d5210f.dmp Operating system: Windows NT 5.1.2600 Service Pack 2 CPU: x86 GenuineIntel family 6 model 23 stepping 10 2 CPUs Crash reason: EXCEPTION_BREAKPOINT Crash address: 0xd42fe5 Thread 0 (crashed) 0 mozjs.dll!js::gc::PushMarkStack [Marking.cpp:0e8f4d4d62fe : 568 + 0x65] eip = 0x00d42fe5 esp = 0x0012c210 ebp = 0x0012c258 ebx = 0x041be710 esi = 0x05ed5480 edi = 0x10261440 eax = 0x00000000 ecx = 0x30f5a25e edx = 0x10361f48 efl = 0x00000212 Found by: given as instruction pointer in context 1 MSVCR100D.dll + 0x6143f eip = 0x10261440 esp = 0x0012c214 ebp = 0x0012c258 Found by: stack scanning 2 mozjs.dll!js::GCMarker::drainMarkStack(js::SliceBudget &) [Marking.cpp:0e8f4d4d62fe : 1258 + 0x7] eip = 0x00d4a378 esp = 0x0012c260 ebp = 0x0012c274 Found by: previous frame's frame pointer 3 mozjs.dll!DrainMarkStack [jsgc.cpp:0e8f4d4d62fe : 4126 + 0x12] eip = 0x00ac5154 esp = 0x0012c27c ebp = 0x0012c294 Found by: call frame info 4 mozjs.dll!IncrementalCollectSlice [jsgc.cpp:0e8f4d4d62fe : 4187 + 0xa] eip = 0x00aeca21 esp = 0x0012c29c ebp = 0x0012c2c8 Found by: call frame info 5 mozjs.dll!GCCycle [jsgc.cpp:0e8f4d4d62fe : 4392 + 0x10] eip = 0x00aee185 esp = 0x0012c2d0 ebp = 0x0012c2f8 Found by: call frame info 6 mozjs.dll!Collect [jsgc.cpp:0e8f4d4d62fe : 4500 + 0x1d] eip = 0x00aee55a esp = 0x0012c300 ebp = 0x0012c344 Found by: call frame info 7 mozjs.dll!js::GC(JSRuntime *,js::JSGCInvocationKind,js::gcreason::Reason) [jsgc.cpp:0e8f4d4d62fe : 4524 + 0x16] eip = 0x00aee6ea esp = 0x0012c34c ebp = 0x0012c364 Found by: call frame info 8 mozjs.dll!JSCompartment::addDebuggee(JSContext *,js::GlobalObject *) [jscompartment.cpp:0e8f4d4d62fe : 738 + 0x11] eip = 0x00a8f256 esp = 0x0012c36c ebp = 0x0012c388
Whiteboard: [orange] → [orange][js:t]
At least I assume comment 2 is the opt crash flavor of the same situation that produces the assertion failure.
Whiteboard: [orange][js:t] → [js:t]
Resolving WFM keyword:intermittent-failure bugs last modified >3 months ago, whose whiteboard contains none of: {random,disabled,marked,fuzzy,todo,fails,failing,annotated,time-bomb,leave open} There will inevitably be some false positives; for that (and the bugspam) I apologise. Filter on orangewfm.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.