Closed
Bug 782267
Opened 12 years ago
Closed 12 years ago
Intermittent crash in test_browserElement_inproc_OpenWindowDifferentOrigin.html [@ nsTableOuterFrame::Reflow]
Categories
(Core :: Layout: Tables, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: emorley, Unassigned)
References
Details
(Keywords: crash, intermittent-failure)
Crash Data
Rev4 MacOSX Lion 10.7 birch debug test mochitests-2/5 on 2012-08-10 10:56:37 PDT for push 08b0fb32055f slave: talos-r4-lion-069 https://tbpl.mozilla.org/php/getParsedLog.php?id=14298392&tree=Birch { 839 INFO TEST-START | /tests/dom/browser-element/mochitest/test_browserElement_inproc_OpenWindowDifferentOrigin.html TEST-UNEXPECTED-FAIL | /tests/dom/browser-element/mochitest/test_browserElement_inproc_OpenWindowDifferentOrigin.html | Exited with code 1 during test run INFO | automation.py | Application ran for: 0:05:34.145496 INFO | automation.py | Reading PID log: /var/folders/qd/srwd5f710sj0fcl9z464lkj00000gn/T/tmpoz3XcLpidlog Downloading symbols from: http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/birch-macosx64-debug/1344618045/firefox-17.0a1.en-US.mac64.crashreporter-symbols.zip PROCESS-CRASH | /tests/dom/browser-element/mochitest/test_browserElement_inproc_OpenWindowDifferentOrigin.html | application crashed (minidump found) Crash dump filename: /var/folders/qd/srwd5f710sj0fcl9z464lkj00000gn/T/tmp3kJTqn/minidumps/A10418F1-0BE0-4865-89FF-0C6D9F2C4C34.dmp Operating system: Mac OS X 10.7.2 11C74 CPU: amd64 family 6 model 23 stepping 10 2 CPUs Crash reason: EXC_BAD_ACCESS / KERN_INVALID_ADDRESS Crash address: 0x3fbf66b0 Thread 0 (crashed) 0 XUL!nsTableOuterFrame::Reflow [nsTableOuterFrame.cpp : 869 + 0x2e] rbx = 0x00000000 r12 = 0x05387ee0 r13 = 0x13bae340 r14 = 0x5fbf6e40 r15 = 0x5fbf7050 rip = 0x016d74bf rsp = 0x5fbf6670 rbp = 0x5fbf6ae0 Found by: given as instruction pointer in context 1 XUL!nsBlockReflowContext::ReflowBlock [nsBlockReflowContext.cpp : 268 + 0x2b] rbx = 0x5fbf6e40 r12 = 0x00000000 r13 = 0x000091f2 r14 = 0x00000000 r15 = 0x5fbf7020 rip = 0x014a4071 rsp = 0x5fbf6af0 rbp = 0x5fbf6cd0 Found by: call frame info 2 XUL!nsBlockFrame::ReflowBlockFrame [nsBlockFrame.cpp : 3208 + 0x58] rbx = 0x00000000 r12 = 0x00000000 r13 = 0x5fbf7830 r14 = 0x05388338 r15 = 0x05387ee0 rip = 0x014983f2 rsp = 0x5fbf6ce0 rbp = 0x5fbf71e0 Found by: call frame info 3 XUL!nsBlockFrame::ReflowLine [nsBlockFrame.cpp : 2516 + 0x21] rbx = 0x05388338 r12 = 0x5fbf7830 r13 = 0x132c0a48 r14 = 0x5fbf75ef r15 = 0x132c09d0 rip = 0x0149dc41 rsp = 0x5fbf71f0 rbp = 0x5fbf73b0 Found by: call frame info 4 XUL!nsBlockFrame::ReflowDirtyLines [nsBlockFrame.cpp : 2022 + 0x29] rbx = 0x053882f8 r12 = 0x05388338 r13 = 0x00008e6e r14 = 0x132c0a48 r15 = 0x5fbf7830 rip = 0x0149f0ff rsp = 0x5fbf73c0 rbp = 0x5fbf76f0 Found by: call frame info 5 XUL!nsBlockFrame::Reflow [nsBlockFrame.cpp : 1071 + 0xe] rbx = 0x5fbf7a00 r12 = 0x00000000 r13 = 0x00000000 r14 = 0xfffffd6c r15 = 0x132c09d0 rip = 0x014a1586 rsp = 0x5fbf7700 rbp = 0x5fbf7e00 Found by: call frame info 6 XUL!nsBlockReflowContext::ReflowBlock [nsBlockReflowContext.cpp : 268 + 0x2b] rbx = 0x5fbf8160 r12 = 0x00000294 r13 = 0x00000000 r14 = 0xfffffd6c r15 = 0x5fbf8340 rip = 0x014a4071 rsp = 0x5fbf7e10 rbp = 0x5fbf7ff0 Found by: call frame info 7 XUL!nsBlockFrame::ReflowBlockFrame [nsBlockFrame.cpp : 3208 + 0x58] rbx = 0x00000000 r12 = 0x00000000 r13 = 0x5fbf8b50 r14 = 0x132a1cb0 r15 = 0x132c09d0 rip = 0x014983f2 rsp = 0x5fbf8000 rbp = 0x5fbf8500 Found by: call frame info 8 XUL!nsBlockFrame::ReflowLine [nsBlockFrame.cpp : 2516 + 0x21] rbx = 0x132a1cb0 r12 = 0x5fbf8b50 r13 = 0x132c0928 r14 = 0x5fbf890f r15 = 0x132c08b0 rip = 0x0149dc41 rsp = 0x5fbf8510 rbp = 0x5fbf86d0 Found by: call frame info 9 XUL!nsBlockFrame::ReflowDirtyLines [nsBlockFrame.cpp : 2022 + 0x29] rbx = 0x132c09d0 r12 = 0x132a1cb0 r13 = 0x00000000 r14 = 0x132c0928 r15 = 0x5fbf8b50 rip = 0x0149f0ff rsp = 0x5fbf86e0 rbp = 0x5fbf8a10 }
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
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
•