Closed Bug 1147219 Opened 11 years ago Closed 9 years ago

Missing stack on ICS emulator test run

Categories

(Testing :: General, defect)

Product:
Testing
Component:
General
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: bholley, Unassigned)

References

Details

I'm stuck again, trying to debug a crashtest failure on bug 1142336. We're clearly hanging, but minidump_stackwalk is failing. https://treeherder.mozilla.org/#/jobs?repo=try&revision=772a71f22425 Output contains the below, indicating that the minidump is wrong somehow. Any suggestions on how to proceed? 13:20:22 WARNING - PROCESS-CRASH | http://10.0.2.2:8888/tests/dom/media/test/crashtests/691096-1.html | application crashed [unknown top frame] 13:20:22 INFO - Crash dump filename: /tmp/tmpYOa3gA/4c068d41-4c0c-6515-1996c195-453ec7f3.dmp 13:20:22 INFO - stderr from minidump_stackwalk: 13:20:22 INFO - 2015-03-24 13:20:15: minidump_processor.cc:264: INFO: Processing minidump in file /tmp/tmpYOa3gA/4c068d41-4c0c-6515-1996c195-453ec7f3.dmp 13:20:22 INFO - 2015-03-24 13:20:15: minidump.cc:3815: INFO: Minidump opened minidump /tmp/tmpYOa3gA/4c068d41-4c0c-6515-1996c195-453ec7f3.dmp 13:20:22 INFO - 2015-03-24 13:20:15: minidump.cc:3847: ERROR: Minidump header signature mismatch: (0x0, 0x0) != 0x504d444d 13:20:22 INFO - 2015-03-24 13:20:15: minidump_processor.cc:268: ERROR: Minidump /tmp/tmpYOa3gA/4c068d41-4c0c-6515-1996c195-453ec7f3.dmp could not be read 13:20:22 INFO - 2015-03-24 13:20:15: minidump.cc:3787: INFO: Minidump closing minidump 13:20:22 INFO - 2015-03-24 13:20:15: minidump_stackwalk.cc:529: ERROR: MinidumpProcessor::Process failed 13:20:22 INFO - minidump_stackwalk exited with return code 1 13:20:22 WARNING - PROCESS-CRASH | http://10.0.2.2:8888/tests/dom/media/test/crashtests/691096-1.html | application crashed [unknown top frame] 13:20:22 INFO - Crash dump filename: /tmp/tmpYOa3gA/3397a4ba-f545-c1c3-134e7366-32e20267.dmp 13:20:22 INFO - stderr from minidump_stackwalk: 13:20:22 INFO - 2015-03-24 13:20:15: minidump_processor.cc:264: INFO: Processing minidump in file /tmp/tmpYOa3gA/3397a4ba-f545-c1c3-134e7366-32e20267.dmp 13:20:22 INFO - 2015-03-24 13:20:15: minidump.cc:3815: INFO: Minidump opened minidump /tmp/tmpYOa3gA/3397a4ba-f545-c1c3-134e7366-32e20267.dmp 13:20:22 INFO - 2015-03-24 13:20:15: minidump.cc:3847: ERROR: Minidump header signature mismatch: (0x0, 0x0) != 0x504d444d 13:20:22 INFO - 2015-03-24 13:20:15: minidump_processor.cc:268: ERROR: Minidump /tmp/tmpYOa3gA/3397a4ba-f545-c1c3-134e7366-32e20267.dmp could not be read 13:20:22 INFO - 2015-03-24 13:20:15: minidump.cc:3787: INFO: Minidump closing minidump 13:20:22 INFO - 2015-03-24 13:20:15: minidump_stackwalk.cc:529: ERROR: MinidumpProcessor::Process failed 13:20:22 INFO - minidump_stackwalk exited with return code 1
Flags: needinfo?(ted)
The dump is empty (zeros where the signature ought to be in the header), so either something is racing with the dump writing or we're failing to write the dump.
Flags: needinfo?(ted)
Depends on: 862730
Andrew, is there a chance that the fix in bug 862730 would fix this (i.e. should we retest)? If not, what's the next step?
Flags: needinfo?(ahalberstadt)
No I already tested this with bug 862730, and like I suspected it didn't help. The fact that minidump_stackwalk is being invoked at all means the harness is checking for crashes in the right places. Like ted mentioned, it could be something racing with writing the dump. I've looked into this a bit and can't find any obvious errors in the harness. If the problem lies outside the harness, I'm not sure what the next step is. I'll try and dig around a little more, but don't count on me to figure it out.
Flags: needinfo?(ahalberstadt)
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.