Crash Reporter always has a problem sending report.




Crash Reporting
7 years ago
6 years ago


(Reporter: Rakshith, Unassigned)


1.9.2 Branch
Windows 7

Firefox Tracking Flags

(Not tracked)




7 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv: Gecko/20100713 Firefox/3.6.7
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv: Gecko/20100713 Firefox/3.6.7

The default "send error report" In firefox when it crashes always fails to send the report  with a notification showing "there was an error sending the report"

Reproducible: Always

Steps to Reproduce:
2.send report
3.problem sending report (notification)
Actual Results:  
It never send the crash report and "crash reporting" is an essential feature to fix bugs

Expected Results:  
It should Have been successful sending the message 

It fails since firefox 3.6 version

Comment 1

7 years ago
Are you connected to the internet via a proxy?

Comment 2

7 years ago

Comment 3

7 years ago
can you load about:crashes and click on a report? does that work?
Component: General → Breakpad Integration
Product: Firefox → Toolkit
QA Contact: general → breakpad.integration
Version: unspecified → 1.9.2 Branch
You are talking about the "Mozilla Crash Reporter" program, right? Not "Windows Error Reporter"?
Summary: Send Error Report always has a problem sending report. → Crash Reporter always has a problem sending report.

Comment 5

7 years ago
Yes, Mozilla Crash Reporter
Ok. Can you check the following for me? Open up the Start menu, in the search field paste in "%APPDATA%\Mozilla\Firefox\Crash Reports\submit.log". That should open the crash reporter's log file in Notepad. You should see a bunch of lines that say "Crash report submission failed:". Paste a few lines here (or if they're all the same, just paste one).

Comment 7

7 years ago
There was only one which was successful but the rest were "as below" but with different time/date.

[03/03/10 00:25:50] Crash report submission failed: The operation completed successfully.
Thanks for looking. Unfortunately that's not very useful. :-/

For testing, could you try installing:

It adds a menu item under "Tools" that will let you force a crash. If you do that (just use "Null Pointer Deref"), can you submit the resulting crash? If submitting that fails, then maybe you can try using a packet sniffer to see what's happening.
(Although our reports are submitted via SSL, so that might be tricky.)

Comment 10

7 years ago
I crashed It On a blank page using "Null Pint Deref!" and the reporter reported Successfully.
Can you try timeless' suggestion from comment 3? If you load "about:crashes" in a tab, you'll see a list of crash reports, both submitted and unsubmitted. (The submitted ones will have the last six digits as YYMMDD, so 100723 for a report you submitted today).  If you click on an unsubmitted one, you should see a little spinner, and if it submits correctly it should redirect you to the report page on crash-stats.

Comment 12

7 years ago
Yeah, seems like submitted ones start with "bp". Most of them are unsubmitted and the submitted ones are the comments that I made in this website.But still "Null Pointer Deref" Method worked.


6 years ago
Last Resolved: 6 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.