Closed
Bug 399645
Opened 17 years ago
Closed 17 years ago
Don't get useful crash stats anymore
Categories
(Toolkit :: Crash Reporting, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: bugzilla, Assigned: ted)
References
()
Details
Attachments
(1 file)
(deleted),
application/octet-stream
|
Details |
I tested the testcase from bug 399013. All four tests resulted in crash reports without any infos.
Those are the Crash IDs:
bp-0fa81e59-790f-11dc-83dd-001a4bd43ed6
bp-1a58c991-790f-11dc-9423-001a4bd43e5c
bp-2458b9cc-790f-11dc-8e3f-001a4bd43ef6
bp-3dd82175-790f-11dc-9bd6-001a4bd43ed6
All tests were made with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a9pre) Gecko/2007101204 Minefield/3.0a9pre, but I also don't get anything useful from latest SeaMonkey nightlies.
Comment 1•17 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a9pre) Gecko/2007101310 Minefield/3.0a9pre
I see something similar I think nearly as long as Breakpad exists:
bp-c8c3087a-79b7-11dc-be5b-001a4bd43e5c
Assignee | ||
Comment 2•17 years ago
|
||
So here's the culprit:
2007-10-17 21:22:23: minidump.cc:2094: ERROR: MinidumpModuleList could not read module auxiliary data for module 36/62
At least one of the modules in the module list is screwy, and the processor gives up processing the module list if that happens, so you don't get any modules, so you get a crap stack. I'm going to file this over at the Breakpad site. FWIW, you still wouldn't get a good stack with those builds anyway, since they're hourly builds.
Assignee | ||
Comment 3•17 years ago
|
||
Assignee | ||
Comment 4•17 years ago
|
||
Also, the module it's dying on is C:\WINDOWS\system32\Syncor11.dll, which Google says is an audio driver, fwiw.
Assignee | ||
Updated•17 years ago
|
Assignee: nobody → ted.mielczarek
Assignee | ||
Comment 5•17 years ago
|
||
Ok, we've updated the processor on the staging server. Can you try submitting a crash report there so we can see if it will work properly? If so, we can get production updated.
In your environment, set MOZ_CRASHREPORTER_URL=http://crash-reports.stage.mozilla.com/submit then submit a crash report. You'll be able to look it up at http://crash-reports.stage.mozilla.com/reports/
Thanks!
Reporter | ||
Comment 6•17 years ago
|
||
I needed some time to get it to work, but finally there was a crash report with correct symbols: http://crash-reports.stage.mozilla.com/reports/report/index/69e1414a-8649-11dc-af36-001321b0783d
The same testcase from bug 368183 shows the old problem on production: 272e667a-864a-11dc-b1dc-001a4bd43ed6
In both cases I used Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a6pre) Gecko/20070701 Minefield/3.0a6pre.
Assignee | ||
Comment 7•17 years ago
|
||
Ok, I'll leave this open until we get that fix rolled out to production in bug 400437. Thanks for verifying.
Comment 8•17 years ago
|
||
Should be fixed, could someone reopen if there are still issues?
Assignee | ||
Updated•17 years ago
|
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Comment 9•17 years ago
|
||
I still get very dull breakpad reports:
http://crash-stats.mozilla.com/report/index/f703800a-d7fe-11dc-8cbd-001a4bd43ed6
Assignee | ||
Comment 10•17 years ago
|
||
That looks like you're using an hourly, not a nightly. We have a bug on getting symbols uploaded for hourlies, but it's not a big priority.
Comment 11•17 years ago
|
||
Crash reason: no crash. (Bug 419326)
http://crash-stats.mozilla.com/report/index/5596a559-e334-11dc-81a7-001a4bd43e5c
Assignee | ||
Comment 12•17 years ago
|
||
Not related. Looks like you hit an invalid parameter handler or something. We had a bug on that, but it's definitely filed upstream:
http://code.google.com/p/google-breakpad/issues/detail?id=170
You need to log in
before you can comment on or make changes to this bug.
Description
•