Intermittent TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser/browser_624727.js | application timed out after 330 seconds with no output

RESOLVED WORKSFORME

Status

()

RESOLVED WORKSFORME
7 years ago
6 years ago

People

(Reporter: mbrubeck, Unassigned)

Tracking

({intermittent-failure})

Trunk
x86
Windows XP
intermittent-failure
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

7 years ago
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1307812026.1307813588.13761.gz

Rev3 WINNT 5.1 mozilla-central opt test mochitest-other on 2011/06/11 10:07:06 

TEST-START | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser/browser_624727.js
TEST-PASS | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser/browser_624727.js | we start off with one tab
TEST-PASS | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser/browser_624727.js | no pinned tabs so far
TEST-PASS | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser/browser_624727.js | there are two tabs, now
TEST-PASS | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser/browser_624727.js | both tabs are now pinned
TEST-PASS | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser/browser_624727.js | one tab left after setBrowserState()
TEST-PASS | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser/browser_624727.js | there are no pinned tabs
TEST-PASS | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser/browser_624727.js | first tab's browser got re-used
TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser/browser_624727.js | application timed out after 330 seconds with no output
INFO | automation.py | Application ran for: 0:11:41.437000
INFO | automation.py | Reading PID log: c:\docume~1\cltbld\locals~1\temp\tmpwd3wnppidlog
==> process 1348 launched child process 4052
INFO | automation.py | Checking for orphan process with PID: 4052
PROCESS-CRASH | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser/browser_624727.js | application crashed (minidump found)
Operating system: Windows NT
                  5.1.2600 Service Pack 2
CPU: x86
     GenuineIntel family 6 model 23 stepping 10
     2 CPUs

Crash reason:  EXCEPTION_ACCESS_VIOLATION_WRITE
Crash address: 0x0

Thread 31 (crashed)
 0  crashinjectdll.dll!CrashingThread(void *) [crashinjectdll.cpp:bfcc94f3fd0a : 13 + 0x0]
    eip = 0x01c51000   esp = 0x134affb8   ebp = 0x134affec   ebx = 0x00000000
    esi = 0x57565554   edi = 0x53525150   eax = 0x00000000   ecx = 0x134affb0
    edx = 0x7c90eb94   efl = 0x00010246
    Found by: given as instruction pointer in context
 1  kernel32.dll + 0xb50a
    eip = 0x7c80b50b   esp = 0x134affbc   ebp = 0x134affec
    Found by: call frame info
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → WORKSFORME
(Assignee)

Updated

6 years ago
Keywords: intermittent-failure
(Assignee)

Updated

6 years ago
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.