Closed
Bug 774010
Opened 12 years ago
Closed 12 years ago
Intermittent test_getElementsByTagNameNS04.html | Exited with code 1 during test run [@js::gc::MarkInternal<JSObject>]
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: RyanVM, Unassigned)
References
Details
(Keywords: crash, intermittent-failure, Whiteboard: [test which aborts the suite])
https://tbpl.mozilla.org/php/getParsedLog.php?id=13524096&tree=Mozilla-Inbound Rev4 MacOSX Snow Leopard 10.6 mozilla-inbound debug test mochitests-3/5 on 2012-07-14 02:56:13 PDT for push 6bfce37d7fa4 slave: talos-r4-snow-041 8895 INFO TEST-START | /tests/dom/tests/mochitest/dom-level2-core/test_getElementsByTagNameNS04.html ++DOMWINDOW == 2049 (0x179057800) [serial = 4260] [outer = 0x127ad5bc0] TEST-UNEXPECTED-FAIL | /tests/dom/tests/mochitest/dom-level2-core/test_getElementsByTagNameNS04.html | Exited with code 1 during test run INFO | automation.py | Application ran for: 0:10:59.960865 INFO | automation.py | Reading PID log: /var/folders/Hs/HsDn6a9SG8idoIya6p9mtE+++TI/-Tmp-/tmpQmpJnFpidlog Downloading symbols from: http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-inbound-macosx64-debug/1342258821/firefox-16.0a1.en-US.mac64.crashreporter-symbols.zip PROCESS-CRASH | /tests/dom/tests/mochitest/dom-level2-core/test_getElementsByTagNameNS04.html | application crashed (minidump found) Crash dump filename: /var/folders/Hs/HsDn6a9SG8idoIya6p9mtE+++TI/-Tmp-/tmpn_ACis/minidumps/F48CCA17-7D3B-433C-8F18-F416A39A2E9C.dmp Operating system: Mac OS X 10.6.8 10K549 CPU: amd64 family 6 model 23 stepping 10 2 CPUs Crash reason: EXC_BAD_ACCESS / KERN_INVALID_ADDRESS Crash address: 0x7b3c3000 Thread 0 (crashed) 0 XUL!js::gc::MarkInternal<JSObject> [Heap.h : 963 + 0x0] rbx = 0x061d4230 r12 = 0x7b3c3f40 r13 = 0x00000000 r14 = 0x7b19e578 r15 = 0x7b3c3000 rip = 0x03f02068 rsp = 0x5fbfae30 rbp = 0x5fbfae60 Found by: given as instruction pointer in context 1 XUL!js::gc::MarkObjectRange [Marking.cpp : 164 + 0xa] rbx = 0x7b19e578 r12 = 0x061d4230 r13 = 0x00000000 r14 = 0x00000001 r15 = 0x0411da3c rip = 0x03efb644 rsp = 0x5fbfae70 rbp = 0x5fbfaea0 Found by: call frame info 2 XUL!JSScript::markChildren [jsscript.cpp : 2105 + 0x14] rbx = 0x00000005 r12 = 0x7b382550 r13 = 0x061d4230 r14 = 0x7b3c3f28 r15 = 0x7b382000 rip = 0x03dabff0 rsp = 0x5fbfaeb0 rbp = 0x5fbfaed0 Found by: call frame info 3 XUL!js::gc::MarkInternal<JSScript> [Marking.cpp : 772 + 0xa] rbx = 0x061d4230 r12 = 0x7b382550 r13 = 0x00000000 r14 = 0x7b3c3f28 r15 = 0x7b382000 rip = 0x03f01e5e rsp = 0x5fbfaee0 rbp = 0x5fbfaf10 Found by: call frame info 4 XUL!fun_trace [jsfun.cpp : 489 + 0x12] rbx = 0x7b3c3f00 r12 = 0x061d4230 r13 = 0x061d4000 r14 = 0x061d4230 r15 = 0x061d4230 rip = 0x03ca62de rsp = 0x5fbfaf20 rbp = 0x5fbfaf30 Found by: call frame info 5 XUL!js::GCMarker::processMarkStackTop [Marking.cpp : 1205 + 0x8] rbx = 0x7b37d1a0 r12 = 0x5fbfb040 r13 = 0x061d4000 r14 = 0x061d4230 r15 = 0x061d4230 rip = 0x03f02dea rsp = 0x5fbfaf40 rbp = 0x5fbfafc0 Found by: call frame info 6 XUL!js::GCMarker::drainMarkStack [Marking.cpp : 1249 + 0xa] rbx = 0x061d4230 r12 = 0x5fbfb040 r13 = 0x061d4000 r14 = 0x061d4230 r15 = 0x061d4000 rip = 0x03efeb3b rsp = 0x5fbfafd0 rbp = 0x5fbfaff0 Found by: call frame info 7 XUL!IncrementalMarkSlice [jsgc.cpp : 3694 + 0xb] rbx = 0x061d4360 r12 = 0x061d4a60 r13 = 0x061d4000 r14 = 0x061d4230 r15 = 0x061d4000 rip = 0x03cbbdb7 rsp = 0x5fbfb000 rbp = 0x5fbfb090 Found by: call frame info 8 XUL!GCCycle [jsgc.cpp : 3845 + 0x12] rbx = 0x5d674948 r12 = 0x00000014 r13 = 0x5d674818 r14 = 0x5fbfb0f0 r15 = 0x061d4000 rip = 0x03cc14fd rsp = 0x5fbfb0a0 rbp = 0x5fbfb140 Found by: call frame info 9 XUL!Collect [jsgc.cpp : 3958 + 0x14] rbx = 0x061d4000 r12 = 0x061d4360 r13 = 0x00000001 r14 = 0x0000062f r15 = 0x00000019 rip = 0x03cc1c3f rsp = 0x5fbfb150 rbp = 0x5fbfb1b0
This bug was observed only on one or more of the six machines listed in bug 787281 comment 11, which seem likely to have bad memory, disk, or other hardware problem, based on the rate of failures on those machines and the types of failures observed. Therefore I'm marking this bug invalid, though it should be reopened if it occurs on other (more reliable) hardware.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
Updated•12 years ago
|
Keywords: intermittent-failure
Updated•12 years ago
|
Whiteboard: [orange][test which aborts the suite] → [test which aborts the suite]
You need to log in
before you can comment on or make changes to this bug.
Description
•