767904 - Intermittent crash during sessionstore/test/browser_408470.js [@ 0x90271bde0]

Status: RESOLVED INVALID

(Firefox :: Session Restore, defect)

Description

[Ed Morley [:emorley]]

Extremely helpful stack :-(

Rev4 MacOSX Snow Leopard 10.6 mozilla-inbound opt test mochitest-other on 2012-06-22 13:49:07 PDT for push aaff24d3411a

slave: talos-r4-snow-041

https://tbpl.mozilla.org/php/getParsedLog.php?id=12911423&tree=Mozilla-Inbound

{
TEST-START | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser_408470.js
TEST-PASS | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser_408470.js | restored stylesheet default
TEST-PASS | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser_408470.js | restored stylesheet alternate
TEST-PASS | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser_408470.js | restored stylesheet altERnate
TEST-PASS | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser_408470.js | restored stylesheet media_empty
TEST-PASS | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser_408470.js | restored stylesheet media_all
TEST-PASS | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser_408470.js | restored stylesheet media_ALL
TEST-PASS | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser_408470.js | restored stylesheet media_screen
TEST-PASS | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser_408470.js | restored stylesheet media_print_screen
TEST-PASS | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser_408470.js | didn't restore stylesheet fail_media_print
TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser_408470.js | Exited with code 1 during test run
INFO | automation.py | Application ran for: 0:04:18.130456
INFO | automation.py | Reading PID log: /var/folders/Hs/HsDn6a9SG8idoIya6p9mtE+++TI/-Tmp-/tmp2enOFSpidlog
Downloading symbols from: http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-inbound-macosx64/1340394883/firefox-16.0a1.en-US.mac.crashreporter-symbols.zip
PROCESS-CRASH | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser_408470.js | application crashed (minidump found)
Crash dump filename: /var/folders/Hs/HsDn6a9SG8idoIya6p9mtE+++TI/-Tmp-/tmpoPO0rT/minidumps/2D7884F6-43B5-4278-BB44-BE1F53EC1BDD.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: 0x271bde0

Thread 0 (crashed)
 0  0x90271bde0
    rbx = 0x06d61328   r12 = 0x2ce78680   r13 = 0x00000000   r14 = 0xffffffff
    r15 = 0x2ce78680   rip = 0x0271bde0   rsp = 0x5fbfa458   rbp = 0x5fbfa4f0
    Found by: given as instruction pointer in context

Thread 1
 0  libSystem.B.dylib + 0x19c0a
    rbx = 0x000cfe50   r12 = 0x70f0f998   r13 = 0x70f0fd68   r14 = 0xffffffff
    r15 = 0x70f0fda8   rip = 0x87eebc0a   rsp = 0x000cfce8   rbp = 0x000cfe90
    Found by: given as instruction pointer in context
 1  libSystem.B.dylib + 0x1badc
    rip = 0x87eedadd   rsp = 0x000cfcf0
    Found by: stack scanning
 2  libSystem.B.dylib + 0x1ca9a
    rip = 0x87eeea9b   rsp = 0x000cfd50
    Found by: stack scanning
 3  libSystem.B.dylib + 0x1c92c
    rip = 0x87eee92d   rsp = 0x000cfd70
    Found by: stack scanning
 4  libSystem.B.dylib + 0x1c78a
    rip = 0x87eee78b   rsp = 0x000cfdc0
    Found by: stack scanning
 5  libSystem.B.dylib + 0x19c27
    rip = 0x87eebc28   rsp = 0x000cfdf0
    Found by: stack scanning
 6  libSystem.B.dylib + 0x1b795
    rip = 0x87eed796   rsp = 0x000cfe10
    Found by: stack scanning
}

Comment 1

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

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.