Closed Bug 1217736 Opened 9 years ago Closed 9 years ago

[MTBF] crash in EMPTY: no crashing thread identified

Categories

(Firefox OS Graveyard :: MTBF, defect)

ARM
Gonk (Firefox OS)
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bobby.chien+bugzilla, Unassigned)

References

Details

(Keywords: crash)

Crash Data

This bug was filed from the Socorro interface and is 
report bp-904ee0ff-34b1-4e0f-8e0c-ff40a2151022.
=============================================================

Paul and Shako, Please help to investigate why crash report was submitted as empty. Thanks.
[From Ted Mielczarek <ted@mozilla.com>]

It looks like that script was out-of-date with what crash-stats expects nowadays. I pushed a little fix to that repository, try grabbing the latest revision of the script, that should work:
http://hg.mozilla.org/users/tmielczarek_mozilla.com/crashsubmit/file/035f56e46f72/submit.py
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.