678596 - Intermittent TEST-UNEXPECTED-FAIL | /tests/layout/style/test/test_visited_lying.html | application timed out after 330 seconds with no output | application crashed

Status: RESOLVED WORKSFORME

(Core :: CSS Parsing and Computation, defect)

Description

[Matt Brubeck (:mbrubeck)]

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1313168735.1313169568.8041.gz
Rev3 WINNT 5.1 mozilla-central opt test mochitests-4/5 on 2011/08/12 10:05:35 
s: talos-r3-xp-046

101554 INFO TEST-START | /tests/layout/style/test/test_visited_lying.html
TEST-UNEXPECTED-FAIL | /tests/layout/style/test/test_visited_lying.html | application timed out after 330 seconds with no output
INFO | automation.py | Application ran for: 0:08:55.797000
INFO | automation.py | Reading PID log: c:\docume~1\cltbld\locals~1\temp\tmp3fcq3mpidlog
==> process 3304 launched child process 4072
INFO | automation.py | Checking for orphan process with PID: 4072
PROCESS-CRASH | /tests/layout/style/test/test_visited_lying.html | application crashed (minidump found)
Crash dump filename: c:\docume~1\cltbld\locals~1\temp\tmpaoiztw\minidumps\60bfaa5b-b5b0-4f78-8c3d-5a80c0983a51.dmp
/var/www/html/stackwalker/minidump_stackwalk /tmp/tmp9yjGtN /builds/stackwalker_symbols/eb10178fb07bddda1e9c2a20ca3ecd9d
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 26 (crashed)
 0  crashinjectdll.dll!CrashingThread(void *) [crashinjectdll.cpp:3c8f87c6cbc6 : 13 + 0x0]
    eip = 0x02e11000   esp = 0x07cfffb8   ebp = 0x07cfffec   ebx = 0x00000000
    esi = 0x57565554   edi = 0x53525150   eax = 0x00000000   ecx = 0x07cfffb0
    edx = 0x7c90eb94   efl = 0x00010246
    Found by: given as instruction pointer in context
 1  kernel32.dll + 0xb50a
    eip = 0x7c80b50b   esp = 0x07cfffbc   ebp = 0x07cfffec
    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