408094 - Firefox crashes fatally when a vpn's proxy is set but network is not on vpn proxy, and a new update (to firefox or add-in) has been found

Status: RESOLVED INCOMPLETE

(Toolkit :: Application Update, defect)

Description

[Ali Mac]

User-Agent:       Opera/9.23 (Windows NT 5.1; U; en)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11

I set a proxy on Firefox while I am in my office's VPN. When I disconnect from that VPN, sometimes I forget to reset the proxy to 'None'.

At a later time when I launch Firefox and it still has the proxy set, let us say that at this point in time a new update for an add-in is found. Right now, I am NOT logged into my office's VPN.

Firefox asks me whether or not I would like to download the update to the add-in. I choose to download the add-in. So, Firefox tries to wind through the proxy, which it does not find because I am not on VPN, in order to download the latest update. It fails to resolve the proxy, is not able to download the update, and crashes fatally. When I re-launch it, it keeps crashing and keeps sending messages to the server about the crash. I have to re-install Firefox before I am able to get it to run again. By the way, if I choose not to download the update, it does not make a difference to the end result - Firefox still crashes.

I use Switch-Proxy to set proxy on my Firefox browser. But the problem has occurred with or without it. I have seen this behaviour consistenly whenever there is a new update for any add-in, or Firefox itself, and I have a proxy set while not on VPN - for about a year now :-). Just never got around to reporting the bug until today.

Reproducible: Always

Steps to Reproduce:
1. Connect to VPN. Set proxy and browse. Disconnect from VPN, but let proxy be. Close browser.
2. Hope that there is a new update to an add-in or Firefox.
3. Launch browser. When asked to download the update, choose Yes (or No). This is when the crash occurs.
Actual Results:  
Firefox crashes and sends messages to the server about the crash. It does not cease to crash until a fresh install of Firefox is performed.

Expected Results:  
Once a proxy is not found, Firefox should cease to download the update and not crash. It should just provide an error message and ask for the proxy to be reset.

Please help. I work at a client who would only use Firefox enterprise-wide. This is almost a fortnightly scenario if not more frequent. I have several Firefox add-ins and one or the other has an update available everyone now and then. I perform the crashing-and-reinstalling ritual quite frequently. In the office I am always on proxy, it is a problem when I come home and have forgotten to switch off the proxy.

Comment 1

[Ali Mac]

If the user can at least have an option for the proxy to be reset to Direct Connection to Internet everytime the browser launches, that might be one way to solve the issue. Please help.

Comment 2

[Nick Thomas [:nthomas] (UTC+12)]

It would really really help if you could submit some crash reports. This page has info on how that works,
   http://support.mozilla.com/kb/Quality+Feedback+Agent
Please report back 2 or more incident IDs. 

You can ensure there is an extension with an update by installing an older version, see the "Complete Version History" link near the bottom of any extension page at addons.mozilla.org.

Comment 3

[Dave Townsend [:mossop]]

Without a crash report I don't think we can proceed here. If you can still reproduce in Firefox 3 then please submit a crash report and reopen this bug.

Comment 4

[Ali Mac]

I am sorry, ever since Version 3 Beta was released, I started using V3B to download Version 2 whenever V2 crashed. I totally missed the update dated Feb 18th on this bug. I will try to reproduce this problem and send the crash report.

Regards.

Comment 5

[Ali Mac]

I am not able to find the Talkback agent for Version 3.0.3. I am only able to find it in Version 2.0.0.17. What do I do to get a crash report for 3.0.3, if it were to crash?

Comment 6

[Dave Townsend [:mossop]]

about:crashes will list crash reports submitted by firefox 3.

Please do not keep changing the resolution, currently it is incomplete because there is not enough information to go on to evaluate this report. When we have some crash report you can reopen the bug and it can be looked into in more detail.

Comment 7

[Ali Mac]

Please tell me how to get the talkback agent installed with FF V 3.0.3.

Comment 8

[Dave Townsend [:mossop]]

There is no talkback for Firefox 3. Firefox 3 includes its own new crash reporter.

I repeat please stop changing the resolution of this bug. If you change it to FIXED again I will assume that the problem is actually fixed and stop monitoring it.