Closed Bug 768453 Opened 12 years ago Closed 12 years ago

Intermittent crash in browser_disablechrome.js [@ js::GCMarker::processMarkStackTop(js::SliceBudget &)|nspr4.dll@0x1642f]

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 profiling opt test mochitest-other on 2012-06-26 06:21:57 PDT for push d29c6d9ad1cb

slave: talos-r3-w7-038

https://tbpl.mozilla.org/php/getParsedLog.php?id=13001668&tree=Profiling

{
TEST-INFO | chrome://mochitests/content/browser/browser/base/content/test/browser_disablechrome.js | Switch back
TEST-PASS | chrome://mochitests/content/browser/browser/base/content/test/browser_disablechrome.js | Attribute should be set
TEST-PASS | chrome://mochitests/content/browser/browser/base/content/test/browser_disablechrome.js | Toolbar should be hidden
TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/base/content/test/browser_disablechrome.js | Exited with code 253 during test run
INFO | automation.py | Application ran for: 0:01:05.974000
INFO | automation.py | Reading PID log: c:\users\cltbld\appdata\local\temp\tmpgoqfxtpidlog
==> process 1776 launched child process 1100
INFO | automation.py | Checking for orphan process with PID: 1100
Downloading symbols from: http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/profiling-win32/1340712079/firefox-16.0a1.en-US.win32.crashreporter-symbols.zip
PROCESS-CRASH | chrome://mochitests/content/browser/browser/base/content/test/browser_disablechrome.js | application crashed (minidump found)
Crash dump filename: c:\users\cltbld\appdata\local\temp\tmpzme65e\minidumps\5be1f0c1-f4d5-444a-8450-abbde5e1f867.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: 0xfffffffff28aea20

Thread 0 (crashed)
 0  mozjs.dll!js::GCMarker::processMarkStackTop(js::SliceBudget &) [Marking.cpp:d29c6d9ad1cb : 1171 + 0x0]
    eip = 0x727e87b0   esp = 0x0030d060   ebp = 0x1f9007a0   ebx = 0x062350f0
    esi = 0x1f9007a0   edi = 0x1f901850   eax = 0xf28ae9e8   ecx = 0x00000201
    edx = 0x1f4d9e00   efl = 0x00010202
    Found by: given as instruction pointer in context
 1  nspr4.dll + 0x1642f
    eip = 0x73976430   esp = 0x0030d080   ebp = 0x1f9007a0
    Found by: stack scanning
 2  mozjs.dll!js::GCMarker::drainMarkStack(js::SliceBudget &) [Marking.cpp:d29c6d9ad1cb : 1226 + 0x7]
    eip = 0x727e8a50   esp = 0x0030d09c   ebp = 0x1f9007a0
    Found by: stack scanning
 3  mozjs.dll!IncrementalMarkSlice [jsgc.cpp:d29c6d9ad1cb : 3630 + 0xf]
    eip = 0x7271b2ef   esp = 0x0030d0ac   ebp = 0x0030d108
    Found by: stack scanning
 4  nspr4.dll + 0x1642f
    eip = 0x73976430   esp = 0x0030d0b8   ebp = 0x0030d108
    Found by: stack scanning
}
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.