Closed Bug 461586 Opened 16 years ago Closed 16 years ago

Crashreporter fails to submit reports

Categories

(Toolkit :: Crash Reporting, defect)

Product:
Toolkit
Component:
Crash Reporting
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
major

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: djcater+bugzilla, Unassigned)

Details

No description provided.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → INCOMPLETE
Oops - premature submit. Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b2pre) Gecko/20081024 Minefield/3.1b2pre When Firefox crashes the crash reporter appears. I fill in the fields and submit. No errors appear so I assume that it has worked. Today I wanted to find one of the reports on crash-stats but couldn't. about:crashes shows no recent crashes. To my (unpleasant) surprise there are 20 .dmp and 20 .extra files in my ~/.mozilla/firefox/Crash Reports/pending/ folder! Running from the command line I can see that there is a small amount of network activity after submitting and then this output: Assertion failure: !"I/O method is invalid", at ../../../../mozilla/nsprpub/pr/src/io/priometh.c:113 submit.log is empty.
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---
Status: REOPENED → NEW
Summary: Crashreporter → Crashreporter fails to submit reports
That assertion isn't from the crashreporter, it doesn't use NSPR.
Yeah, this is a problem somewhere between my local copy of curl, NSS and NSPR.
Status: NEW → RESOLVED
Closed: 16 years ago → 16 years ago
Resolution: --- → INVALID
of worth http://mxr.mozilla.org/mozilla-central/source/nsprpub/pr/src/io/priometh.c#113 assertion failures from NSPR are fatal. you won't get a stack trace, it just kills itself. you need a debugger attached before the failure in order to catch it.
You need to log in before you can comment on or make changes to this bug.