Open Bug 405932 Opened 17 years ago Updated 1 year ago

Crash Reporter does not send crash reports with .pac proxy

Categories

(Toolkit :: Crash Reporting, defect, P2)

Product:
Toolkit
Component:
Crash Reporting
Platform:
x86
Windows XP
Type:
defect

Tracking

()

People

(Reporter: coluf, Unassigned)

References

(
URL
)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b1) Gecko/2007110904 Firefox/3.0b1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b1) Gecko/2007110904 Firefox/3.0b1

Crash Reporter correctly records crash reports but does not send them.  After a crash, Firefox restarts but states it cannot send the crash report.

My current hypothesis is that Crash Reporter cannot resolve the correct proxy IP address if Firefox is configured to use a .pac (proxy auto-config) file.



Reproducible: Always

Steps to Reproduce:
1.  Firefox is working and accessing the web.
2.  Firefox fatally crashes and Crash Reporter correctly makes a crash report.
3.  On restarting, Firefox tries once to send crash report and fails.
Actual Results:  
Crash reports are sitting in the 'Application Data\Mozilla\Firefox\Crash Reports\pending' waiting to be sent.

Expected Results:  
Crash reports should have been sent.

Firefox crashed repeatably when used with the EMC Documentum Webtop application (version 5.3.0.414 SP4).  This was the cause for Crash Reporter to trap the report and attempt to send it.
.pac is set as a web address of the format 'http://somecompany.com/poxyAutoconfig.pac'.  It is set in Options > Advanced > Network > (Connection) Settings.
Please use the right components when filling bugs
Component: General → Breakpad Integration
Product: Firefox → Toolkit
QA Contact: general → breakpad.integration
The crash reporter uses your system internet configuration, not Firefox's.  Do you have this proxy configured in IE?

Hi Ted

Yes.  IE has been configured to use the same Autoconfig Proxy file as FireFox.  I can use both browsers with the same configuration.

I see this bug as important as it prevents crash reports from many enterprises and thus bug reports may miss a significant sector of users.  And it was an enterprise application, Documentum, that triggers the FireFox crash (not used by home users).

Is there some way that I can ask Crash Reporter to retry sending the files?  Or is there some way to manually send the files (say email) to Bugzilla?


This is going to require more investigation.

confirming based on the dupe
Status: UNCONFIRMED → NEW
Ever confirmed: true
Ok, this must either be the way your proxy PAC is set up, or your proxy itself.  I setup a simple proxy pac that pointed to a local squid server, and I was able to successfully submit a crash report through it.  Can you try loading https://crash-reports.mozilla.com/submit in IE?  If that fails, then there's definitely something with your proxy or the pac that's making this fail.

With IE or Minefield I get access to "Mozilla Crash Reports" and I am able with both to read reports.
I tried to browse the source code to see how the code worked. Only had some luck.

I found documentation on the Windows functions to get the proxy configuration: WinHTTP AutoProxy Functions
http://msdn2.microsoft.com/en-us/library/aa384122.aspx

I think the function that processes the proxy file is 'WinHttpGetProxyForUrl'.  I could not see it used in the source code.

Ok, you're right, although the sender code uses WinINET and not WinHTTP, so the right URL is:
http://msdn2.microsoft.com/en-us/library/aa383910.aspx

I filed this upstream in Breakpad:
http://code.google.com/p/google-breakpad/issues/detail?id=232

Apparently my testing wasn't really thorough enough.  Sorry about that.

What protocol is used for reporting crash ?
If ftp is used, as it is forbidden by our information system security, the report could not be send.
Have you an alternative to send you crash reports ?

From 11/26/2007 to today I get 21 crashes ....
It's HTTPS, but the code doesn't support PAC proxies.  I've filed it in the Breakpad issue tracking system, that's the best I can do right now.
Flags: blocking1.9?
Flags: blocking1.9? → blocking1.9+
Priority: -- → P2
It happens also on Ubuntu 7.10
Every time FF3 crashes, it displays the crash report window, then it attempts to send the report, and it crashes (FF doesn't open as it supposed to be).

I think that this bug should be in high priority because many other bugs are not submitted, and hence, not discovered, because the reporter crashes!
That's not the same issue, this bug is only for Windows.  You may be seeing bug 407748.


Thanks.

But I suggest writing the bug solution in a more public/viewed page.
Flags: tracking1.9+ → wanted1.9.0.x+
(In reply to comment #16)
Stop bothering developers with this minor problem, you are the only one, who has it.
(In reply to comment #17)
> (In reply to comment #16)
> Stop bothering developers with this minor problem, you are the only one, who
> has it.

No, he is not the only one.
excuses for comment 17, some is spamming various bugs, see bug 567347
Severity: normal → S3
Duplicate of this bug: 430469
You need to log in before you can comment on or make changes to this bug.