Closed
Bug 633557
Opened 13 years ago
Closed 12 years ago
sporadic "TEST-UNEXPECTED-FAIL | Shutdown | Exited with code 1 during test run" during mochitest-browser-chrome shutdown, with crash in GCGraphBuilder::NoteXPCOMChild
Categories
(Core :: XPCOM, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: dholbert, Unassigned)
References
Details
(Keywords: intermittent-failure)
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1297445901.1297447156.28034.gz Rev3 MacOSX Snow Leopard 10.6.2 mozilla-central opt test mochitest-other on 2011/02/11 09:38:21 s: talos-r3-snow-016 *** End BrowserChrome Test Results *** NOTE: child process received `Goodbye', closing down NOTE: child process received `Goodbye', closing down NOTE: child process received `Goodbye', closing down NOTE: child process received `Goodbye', closing down TEST-UNEXPECTED-FAIL | Shutdown | Exited with code 1 during test run INFO | automation.py | Application ran for: 0:11:16.990484 INFO | automation.py | Reading PID log: /var/folders/H5/H5TD8hgwEqKq9hgKlayjWU+++TM/-Tmp-/tmpWsxxcTpidlog PROCESS-CRASH | Shutdown | application crashed (minidump found) Operating system: Mac OS X 10.6.6 10J567 CPU: amd64 family 6 model 23 stepping 10 2 CPUs Crash reason: EXC_BAD_ACCESS / KERN_INVALID_ADDRESS Crash address: 0x8 NEXT ERROR Thread 3 (crashed) 0 XUL!GCGraphBuilder::NoteXPCOMChild [nsCycleCollector.cpp:409d5db222eb : 1205 + 0x13] rbx = 0x04b80d30 r12 = 0x04b80d30 r13 = 0x00000000 r14 = 0x04b80d30 r15 = 0x701495c0 rip = 0x00e201a7 rsp = 0x04b80c10 rbp = 0x323f13b0 Found by: given as instruction pointer in context 1 XUL!nsXPCWrappedJS::cycleCollection::Traverse [xpcwrappedjs.cpp:409d5db222eb : 78 + 0xb] rbx = 0x04b80d30 r12 = 0x323f13b0 r13 = 0x00000000 r14 = 0x04b80d30 r15 = 0x701495c0 rip = 0x0098ae13 rsp = 0x04b80c80 rbp = 0x323f13a0 Found by: call frame info 2 XUL!nsCycleCollector::BeginCollection [nsCycleCollector.cpp:409d5db222eb : 1523 + 0xe] rbx = 0x21c12cd8 r12 = 0x21c12d00 r13 = 0x00000000 r14 = 0x04b80d30 r15 = 0x21c0d000 rip = 0x00e21394 rsp = 0x04b80d10 rbp = 0x03847600 Found by: call frame info 3 XUL!nsCycleCollectorRunner::Run [nsCycleCollector.cpp:409d5db222eb : 3312 + 0xe] rbx = 0x0331cc60 r12 = 0x00000001 r13 = 0x04b80e40 r14 = 0x00000000 r15 = 0x04b80eac rip = 0x00e2224f rsp = 0x04b80e10 rbp = 0x8000ffff Found by: call frame info 4 XUL!nsThread::ProcessNextEvent [nsThread.cpp:409d5db222eb : 633 + 0x5] rbx = 0x0331ce00 r12 = 0x00000001 r13 = 0x04b80e40 r14 = 0x00000000 r15 = 0x04b80eac rip = 0x00e12b53 rsp = 0x04b80e20 rbp = 0x8000ffff Found by: call frame info 5 XUL!NS_ProcessNextEvent_P [nsThreadUtils.cpp : 250 + 0xc] rbx = 0x00000001 r12 = 0x00000000 r13 = 0x019f3160 r14 = 0x02f01b00 r15 = 0x0331d1d0 rip = 0x00dcead9 rsp = 0x04b80ea0 rbp = 0x0331ce00 Found by: call frame info 6 XUL!nsThread::ThreadFunc [nsThread.cpp:409d5db222eb : 278 + 0xc] rbx = 0x0331d1d0 r12 = 0x00000000 r13 = 0x019f3160 r14 = 0x02f01b00 r15 = 0x0331d1d0 rip = 0x00e12e3d rsp = 0x04b80ec0 rbp = 0x0331ce00 Found by: call frame info 7 libnspr4.dylib!_pt_root [ptthread.c:409d5db222eb : 187 + 0x6] rbx = 0x0331d1d0 r12 = 0x00000000 r13 = 0x00002e07 r14 = 0x02f01b00 r15 = 0x0331d1d0 rip = 0x02f01b9e rsp = 0x04b80f00 rbp = 0x04b80f10 Found by: call frame info 8 libSystem.B.dylib + 0x3a535 rbx = 0x04b81000 r12 = 0x00000000 r13 = 0x00002e07 r14 = 0x02f01b00 r15 = 0x0331d1d0 rip = 0x80c3c536 rsp = 0x04b80f20 rbp = 0x04b80f50 Found by: call frame info 9 libSystem.B.dylib + 0x3a3e8 rip = 0x80c3c3e9 rsp = 0x04b80f60 Found by: stack scanning
|
Reporter | |
Comment 1•13 years ago
|
||
See also Bug 590721 (same crash signature, but during test_jQuery.html)
| Comment hidden (Legacy TBPL/Treeherder Robot) |
| Comment hidden (Legacy TBPL/Treeherder Robot) |
| Comment hidden (Legacy TBPL/Treeherder Robot) |
|
||
Comment 5•12 years ago
|
||
Mass marking whiteboard:[orange] bugs WFM (to clean up TBPL bug suggestions) that:
* Haven't changed in > 6months
* Whose whiteboard contains none of the strings: {disabled,marked,random,fuzzy,todo,fails,failing,annotated,leave open,time-bomb}
* Passed a (quick) manual inspection of bug summary/whiteboard to ensure they weren't a false positive.
I've also gone through and searched for cases where the whiteboard wasn't labelled correctly after test disabling, by using attachment description & basic comment searches. However if the test for which this bug was about has in fact been disabled/annotated/..., please accept my apologies & reopen/mark the whiteboard appropriately so this doesn't get re-closed in the future (and please ping me via IRC or email so I can try to tweak the saved searches to avoid more edge cases).
Sorry for the spam! Filter on: #FFA500Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
|
Assignee | |
Updated•12 years ago
|
Keywords: intermittent-failure
|
|
Assignee | |
Updated•12 years ago
|
Whiteboard: [orange]
You need to log in
before you can comment on or make changes to this bug.
Description
•