672896 - Intermittent TEST-UNEXPECTED-FAIL | /tests/docshell/test/navigation/test_bug279495.html | application timed out after 330 seconds with no output; application crashed

Status: RESOLVED WORKSFORME

(Core :: DOM: Navigation, defect)

Description

[Matt Brubeck (:mbrubeck)]

http://tinderbox.mozilla.org/showlog.cgi?log=Mozilla-Aurora/1311183300.1311183990.5422.gz#err1

Rev3 WINNT 5.1 mozilla-aurora opt test mochitests-2/5 on 2011/07/20 10:35:00 

134 INFO TEST-END | /tests/docshell/test/navigation/test_bug278916.html | finished in 1120ms
135 INFO TEST-START | /tests/docshell/test/navigation/test_bug279495.html
before 528384, after 524288, break 00000000
before 528384, after 524288, break 00000000
TEST-UNEXPECTED-FAIL | /tests/docshell/test/navigation/test_bug279495.html | application timed out after 330 seconds with no output
INFO | automation.py | Application ran for: 0:05:46.609000
INFO | automation.py | Reading PID log: c:\docume~1\cltbld\locals~1\temp\tmpsrzk-rpidlog
PROCESS-CRASH | /tests/docshell/test/navigation/test_bug279495.html | application crashed (minidump found)
Crash dump filename: c:\docume~1\cltbld\locals~1\temp\tmprydlv5\minidumps\18fe31ec-7484-419e-a33d-d00ca83f80c4.dmp
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 22 (crashed)
 0  crashinjectdll.dll!CrashingThread(void *) [crashinjectdll.cpp:e6132405124c : 13 + 0x0]
    eip = 0x02d11000   esp = 0x0555ffb8   ebp = 0x0555ffec   ebx = 0x00000000
    esi = 0x57565554   edi = 0x53525150   eax = 0x00000000   ecx = 0x0555ffb0
    edx = 0x7c90eb94   efl = 0x00010246
    Found by: given as instruction pointer in context
 1  kernel32.dll + 0xb50a
    eip = 0x7c80b50b   esp = 0x0555ffbc   ebp = 0x0555ffec
    Found by: call frame info

Comment 1

[Ed Morley [:emorley]]

Mass marking whiteboard:[orange] bugs WFM (to clean up TBPL bug suggestions) that:
* Haven't changed in > 6months
* Whose whiteboard contains none of the strings: {disabled,marked,random,fuzzy,todo,fails,failing,annotated,leave open,time-bomb}
* Passed a (quick) manual inspection of bug summary/whiteboard to ensure they weren't a false positive.

I've also gone through and searched for cases where the whiteboard wasn't labelled correctly after test disabling, by using attachment description & basic comment searches. However if the test for which this bug was about has in fact been disabled/annotated/..., please accept my apologies & reopen/mark the whiteboard appropriately so this doesn't get re-closed in the future (and please ping me via IRC or email so I can try to tweak the saved searches to avoid more edge cases).

Sorry for the spam! Filter on: #FFA500