Closed Bug 872788 Opened 10 years ago Closed 9 years ago

Frequent PGO Windows 7 and XP iX PROCESS-CRASH | dromaeo_dom | application crashed [Unknown top frame][@ mozalloc_abort(char const * const)] followed by 'timeout exceeded'

Categories

(Testing :: Talos, defect)

Product:
Testing
Component:
Talos
Platform:
x86
Windows 7
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(firefox30 wontfix, firefox31 fixed, firefox32 fixed, firefox-esr24 wontfix)

Status:
RESOLVED FIXED
Milestone:
mozilla32
Tracking Flags:
Tracking Status
firefox30 --- wontfix
firefox31 --- fixed
firefox32 --- fixed
firefox-esr24 --- wontfix

People

(Reporter: philor, Assigned: jmaher)

References

Details

(Keywords: intermittent-failure, Whiteboard: [pgo]) 

https://tbpl.mozilla.org/php/getParsedLog.php?id=22996244&tree=Mozilla-Inbound
Windows 7 32-bit mozilla-inbound pgo talos dromaeojs on 2013-05-15 13:19:07 PDT for push 835e5b42aa10
slave: t-w732-ix-011

Cycle 1(1): loaded http://localhost/page_load_test/dromaeo/dom-attr.html (next: http://localhost/page_load_test/dromaeo/dom-modify.html)
RSS: Main: 192466944


	Screen width/height:1600/1200
	colorDepth:24
	Browser inner width/height: 1008/666


browser_name:Firefox
browser_version:24.0a1
buildID:20130515091549

PROCESS-CRASH | dromaeo_dom | application crashed [Unknown top frame]
Crash dump filename: c:\users\cltbld\appdata\local\temp\tmpbua8b9\profile\minidumps\b4122b86-00e9-489b-9e08-9ef22f9ed6f1.dmp
stderr from minidump_stackwalk:
2013-05-15 14:39:03: minidump_processor.cc:264: INFO: Processing minidump in file c:\users\cltbld\appdata\local\temp\tmpbua8b9\profile\minidumps\b4122b86-00e9-489b-9e08-9ef22f9ed6f1.dmp
cygwin warning:
  MS-DOS style path detected: c:\users\cltbld\appdata\local\temp\tmpbua8b9\profile\minidumps\b4122b86-00e9-489b-9e08-9ef22f9ed6f1.dmp
  Preferred POSIX equivalent is: /cygdrive/c/users/cltbld/appdata/local/temp/tmpbua8b9/profile/minidumps/b4122b86-00e9-489b-9e08-9ef22f9ed6f1.dmp
  CYGWIN environment variable option "nodosfilewarning" turns off this warning.
  Consult the user's guide for more details about POSIX paths:
    http://cygwin.com/cygwin-ug-net/using.html#using-pathnames
2013-05-15 14:39:03: minidump.cc:3815: INFO: Minidump opened minidump c:\users\cltbld\appdata\local\temp\tmpbua8b9\profile\minidumps\b4122b86-00e9-489b-9e08-9ef22f9ed6f1.dmp
2013-05-15 14:39:03: minidump.cc:4086: ERROR: ReadBytes: read 0/32
2013-05-15 14:39:03: minidump.cc:3834: ERROR: Minidump cannot read header
2013-05-15 14:39:03: minidump_processor.cc:268: ERROR: Minidump c:\users\cltbld\appdata\local\temp\tmpbua8b9\profile\minidumps\b4122b86-00e9-489b-9e08-9ef22f9ed6f1.dmp could not be read
2013-05-15 14:39:03: minidump.cc:3787: INFO: Minidump closing minidump
2013-05-15 14:39:03: minidump_stackwalk.cc:529: ERROR: MinidumpProcessor::Process failed

minidump_stackwalk exited with return code 1
Failed dromaeo_dom: 
		Stopped Wed, 15 May 2013 14:39:03
Traceback (most recent call last):
  File "run_tests.py", line 277, in run_tests
    talos_results.add(mytest.runTest(browser_config, test))
  File "C:\slave\talos-data\talos\ttest.py", line 387, in runTest
    raise talosError("timeout exceeded")
talosError: 'timeout exceeded'
Traceback (most recent call last):
  File "run_tests.py", line 330, in <module>
    main()
  File "run_tests.py", line 327, in main
    run_tests(parser)
  File "run_tests.py", line 289, in run_tests
    raise e
utils.talosError: 'timeout exceeded'
program finished with exit code 1

https://tbpl.mozilla.org/php/getParsedLog.php?id=22991966&tree=Mozilla-Inbound
t-w732-ix-019

https://tbpl.mozilla.org/php/getParsedLog.php?id=22988149&tree=Mozilla-Inbound
t-w732-ix-060

https://tbpl.mozilla.org/php/getParsedLog.php?id=22996903&tree=Mozilla-Inbound
t-w732-ix-050
https://tbpl.mozilla.org/php/getParsedLog.php?id=22998759&tree=Mozilla-Inbound
t-w732-ix-041

With just the timeout exceeded, without the empty crash.
I'm undecided about whether the comment 2 timeout, timeout, slave disconnect during tp5 is the same thing or a different thing, so I stuck it here while I thought about it.
Summary: Frequent Windows 7 iX PROCESS-CRASH | dromaeo_dom | application crashed [Unknown top frame] followed by talosError: 'timeout exceeded' → Frequent Windows 7 iX PROCESS-CRASH | dromaeo_dom | application crashed [Unknown top frame][@ mozalloc_abort(char const * const)] followed by talosError: 'timeout exceeded'
Summary: Frequent Windows 7 iX PROCESS-CRASH | dromaeo_dom | application crashed [Unknown top frame][@ mozalloc_abort(char const * const)] followed by talosError: 'timeout exceeded' → Frequent Windows 7 and XP iX PROCESS-CRASH | dromaeo_dom | application crashed [Unknown top frame][@ mozalloc_abort(char const * const)] followed by talosError: 'timeout exceeded'
And see also bug 798219, since for the most part the WinXP iX slaves don't manage to produce the crash, but hellishly frequently hit the timeout exceeded.