820362 - Intermittent minidump_stackwalk "minidump.cc:4086: ERROR: ReadBytes: read 0/32 | minidump.cc:3834: ERROR: Minidump cannot read header"

Status: RESOLVED WORKSFORME

(Toolkit :: Crash Reporting, defect)

Description

[Ed Morley [:emorley]]

Rev3 WINNT 6.1 mozilla-inbound opt test mochitest-2 on 2012-12-06 22:14:11 PST for push 390569a008e5

slave: talos-r3-w7-072

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

{
TEST-UNEXPECTED-FAIL | /tests/dom/imptests/webapps/DOMCore/tests/approved/test_Range-surroundContents.html | Exited with code -2147483645 during test run
INFO | automation.py | Application ran for: 0:04:26.335000
INFO | automation.py | Reading PID log: c:\users\cltbld\appdata\local\temp\tmpjt3xj9pidlog
==> process 2848 launched child process 1976
INFO | automation.py | Checking for orphan process with PID: 1976
Downloading symbols from: http://ftp-scl3.mozilla.com/pub/mozilla.org/firefox/tinderbox-builds/mozilla-inbound-win32/1354858251/firefox-20.0a1.en-US.win32.crashreporter-symbols.zip
PROCESS-CRASH | /tests/dom/imptests/webapps/DOMCore/tests/approved/test_Range-surroundContents.html | application crashed [Unknown top frame]
SUCCESS: The process with PID 3304 has been terminated.
SUCCESS: The process with PID 2180 has been terminated.
SUCCESS: The process with PID 3056 has been terminated.
Crash dump filename: c:\users\cltbld\appdata\local\temp\tmpetzuyp\minidumps\b3ddc05c-85b3-4117-99ef-336d0c07d49c.dmp
stderr from minidump_stackwalk:
2012-12-06 22:21:44: minidump_processor.cc:264: INFO: Processing minidump in file c:\users\cltbld\appdata\local\temp\tmpetzuyp\minidumps\b3ddc05c-85b3-4117-99ef-336d0c07d49c.dmp
cygwin warning:
  MS-DOS style path detected: c:\users\cltbld\appdata\local\temp\tmpetzuyp\minidumps\b3ddc05c-85b3-4117-99ef-336d0c07d49c.dmp
  Preferred POSIX equivalent is: /cygdrive/c/users/cltbld/appdata/local/temp/tmpetzuyp/minidumps/b3ddc05c-85b3-4117-99ef-336d0c07d49c.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
2012-12-06 22:21:44: minidump.cc:3815: INFO: Minidump opened minidump c:\users\cltbld\appdata\local\temp\tmpetzuyp\minidumps\b3ddc05c-85b3-4117-99ef-336d0c07d49c.dmp
2012-12-06 22:21:44: minidump.cc:4086: ERROR: ReadBytes: read 0/32
2012-12-06 22:21:44: minidump.cc:3834: ERROR: Minidump cannot read header
2012-12-06 22:21:44: minidump_processor.cc:268: ERROR: Minidump c:\users\cltbld\appdata\local\temp\tmpetzuyp\minidumps\b3ddc05c-85b3-4117-99ef-336d0c07d49c.dmp could not be read
2012-12-06 22:21:44: minidump.cc:3787: INFO: Minidump closing minidump
2012-12-06 22:21:44: minidump_stackwalk.cc:529: ERROR: MinidumpProcessor::Process failed

minidump_stackwalk exited with return code 1
Saved dump as C:\talos-slave\test/minidumps\b3ddc05c-85b3-4117-99ef-336d0c07d49c.dmp
WARNING | automationutils.processLeakLog() | refcount logging is off, so leaks can't be detected!

INFO | runtests.py | Running tests: end.
}

Comment 1

[Ed Morley [:emorley]]

(See also the other [Unknown top frame] entries in bug 817354)

Comment 2

[(not currently active) Ted Mielczarek]

This just means "we didn't write out a valid minidump". Most likely we're getting a zero-byte file. We should probably have checkForCrashes look for info in the .extra file so we could determine if this was an OOM or what.

Comment 3

[Ed Morley [:emorley]]

(In reply to Ted Mielczarek [:ted.mielczarek] from comment #2)
> This just means "we didn't write out a valid minidump". Most likely we're
> getting a zero-byte file. We should probably have checkForCrashes look for
> info in the .extra file so we could determine if this was an OOM or what.

Ah, thank you :-0

Comment 4

[Ed Morley [:emorley]]

s/0/\)/

Comment 5

[Ed Morley [:emorley]]

(OrangeWFM bugs not modified in > 2 months)