Closed Bug 392001 Opened 18 years ago Closed 17 years ago

Crash Reporter can fail to submit crash reports without attempting to connect

Categories

(Toolkit :: Crash Reporting, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: wildmyron, Unassigned)

Details

From discussion at forums.mozillazine.org Breakpad is failing to submit any reports for some people. I'm filing this based on information provided by malliz through the forum and private email. This is specifically related to current trunk builds of Firefox, but I believe some Seamonkey users are affected as well. STR: 1) Crash Firefox 2) Flush dns cache and monitor network traffic 3) Attempt to submit crash report Actual Results: Crash Reporter says that the attempt to submit failed. There is no network traffic - not even a dns query. The report is on disk in the Pending folder. Disabling the firewall did not allow reports to be sent, but a report could be submitted from a different computer on the same home network. Also tested with clean install of Minefield.
Keywords: qawanted
I can add the fact that Breakpad had successfully sent one report
Further to this I just had a Eureka moment I realized that the one successful report was before this pc was being used as the dial-up gateway for my home network. That is when I was transferring files to it across my network from my old pc that was being used as the gateway at that stage. So I am wondering if it could be either breakpad is not working on dial-up. Or if it is something in my home network set-up?
It used to work on my PC, but now Crash Reporter always fails to submit crash report with the latest nightlies. Using a packet sniffer I checked the hostname that the crashes are being submitted to which is 63.245.209.57 (dyna-crashreports.nslb.sj.mozilla.com). Going to the https://63.245.209.57 in a browser gives an error about a Security Error: Domain Name Mismatch. I also see that a connection to crl.xrampsecurity.com is made which returns a list of revoked certificates and once this is received, CrashReporter.exe immediately closes the connection to 63.245.209.57. Doing a nslookup on 63.245.209.57 results in dyna-crashreports.nslb.sj.mozilla.com, but doing an nslookup on dyna-crashreports.nslb.sj.mozilla.com says it is an unknown host.
This seems to have been resolved by the fix for bug 390568. Not sure if it was the same issue so I'm just going to mark it WFM.
Status: NEW → RESOLVED
Closed: 17 years ago
Keywords: qawanted
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.