Closed Bug 768036 Opened 12 years ago Closed 12 years ago

Intermittent crash in background-common-usage-ref.html [@ js::gc::ScanShape]

Categories

(Core :: JavaScript Engine, defect)

x86
Windows 7
defect
Not set
critical

Tracking

()

RESOLVED INVALID

People

(Reporter: emorley, Unassigned)

References

Details

(Keywords: crash, intermittent-failure, Whiteboard: [js:t][badslave?][talos-r3-w7-038])

Crash Data

Rev3 WINNT 6.1 mozilla-central opt test reftest-no-accel on 2012-06-23 11:10:24 PDT for push a387c891b56f

slave: talos-r3-w7-038

https://tbpl.mozilla.org/php/getParsedLog.php?id=12939264&tree=Firefox

{
REFTEST TEST-START | file:///c:/talos-slave/test/build/reftest/tests/layout/reftests/image-rect/background-common-usage-floating-point.html | 4472 / 7994 (55%)
REFTEST TEST-START | file:///c:/talos-slave/test/build/reftest/tests/layout/reftests/image-rect/background-common-usage-ref.html | 4472 / 7994 (55%)
TEST-UNEXPECTED-FAIL | file:///c:/talos-slave/test/build/reftest/tests/layout/reftests/image-rect/background-common-usage-ref.html | Exited with code -1073741819 during test run
INFO | automation.py | Application ran for: 0:27:20.704000
INFO | automation.py | Reading PID log: c:\users\cltbld\appdata\local\temp\tmpxlmargpidlog
==> process 1936 launched child process 1640
INFO | automation.py | Checking for orphan process with PID: 1640
Downloading symbols from: http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-central-win32/1340469223/firefox-16.0a1.en-US.win32.crashreporter-symbols.zip
PROCESS-CRASH | file:///c:/talos-slave/test/build/reftest/tests/layout/reftests/image-rect/background-common-usage-ref.html | application crashed (minidump found)
Crash dump filename: c:\users\cltbld\appdata\local\temp\tmpaa8qbt\minidumps\88ae1790-4172-47ef-8fa2-d3edb9afe1da.dmp
Operating system: Windows NT
                  6.1.7600 
CPU: x86
     GenuineIntel family 6 model 23 stepping 10
     2 CPUs

Crash reason:  EXCEPTION_ACCESS_VIOLATION_READ
Crash address: 0xffffffff954fffbc

Thread 0 (crashed)
 0  mozjs.dll!js::gc::ScanShape [Marking.cpp:a387c891b56f : 604 + 0x2f]
    eip = 0x6a8f3c22   esp = 0x0047d0c4   ebp = 0x0047d0d4   ebx = 0x00000000
    esi = 0x00000002   edi = 0x954fffbc   eax = 0x0001f7c1   ecx = 0x00000fbe
    edx = 0x95400000   efl = 0x00010286
    Found by: given as instruction pointer in context
 1  mozjs.dll!js::GCMarker::processMarkStackTop(js::SliceBudget &) [Marking.cpp:a387c891b56f : 1167 + 0x7a]
    eip = 0x6a8f4928   esp = 0x0047d0dc   ebp = 0x0047d108
    Found by: call frame info
 2  mozjs.dll!js::GCMarker::drainMarkStack(js::SliceBudget &) [Marking.cpp:a387c891b56f : 1226 + 0x7]
    eip = 0x6a8f4ba0   esp = 0x0047d110   ebp = 0x0047d11c
    Found by: call frame info
 3  mozjs.dll!IncrementalMarkSlice [jsgc.cpp:a387c891b56f : 3630 + 0xe]
    eip = 0x6a82a7f8   esp = 0x0047d124   ebp = 0x0047d148
    Found by: call frame info
 4  mozjs.dll!GCCycle [jsgc.cpp:a387c891b56f : 3784 + 0x10]
    eip = 0x6a82c462   esp = 0x0047d150   ebp = 0x0047d178
    Found by: call frame info
 5  mozjs.dll!Collect [jsgc.cpp:a387c891b56f : 3895 + 0x1a]
    eip = 0x6a82c5f0   esp = 0x0047d180   ebp = 0x0047d19c
    Found by: call frame info
 6  mozjs.dll!js::GCSlice(JSRuntime *,js::JSGCInvocationKind,js::gcreason::Reason) [jsgc.cpp:a387c891b56f : 3925 + 0x20]
    eip = 0x6a82c6b4   esp = 0x0047d1a4   ebp = 0x0047d1bc
    Found by: call frame info
 7  mozjs.dll!js::IncrementalGC(JSRuntime *,js::gcreason::Reason) [jsfriendapi.cpp:a387c891b56f : 149 + 0xe]
    eip = 0x6a821f52   esp = 0x0047d1c4   ebp = 0x0047d1d0
    Found by: call frame info
 8  xul.dll!nsXPConnect::Collect(unsigned int,unsigned int) [nsXPConnect.cpp:a387c891b56f : 383 + 0x5]
    eip = 0x6951976a   esp = 0x0047d1d8   ebp = 0x0047d1e4
}
Depends on: 768489
Whiteboard: [orange] → [orange][badslave?][talos-r3-w7-038]
Whiteboard: [orange][badslave?][talos-r3-w7-038] → [js:t][orange][badslave?][talos-r3-w7-038]
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
Whiteboard: [js:t][orange][badslave?][talos-r3-w7-038] → [js:t][badslave?][talos-r3-w7-038]
You need to log in before you can comment on or make changes to this bug.