Firefox crashes with any version after 36.0.1
Hello,
I work in an environment that uses a very strict proxy to filter all incoming and outgoing internet traffic. Firefox has been our default and primary internet browser, but any version we use beyond 36.0.1 crashes and is blocked by our proxy when trying to access any internet site.
Can anyone help inform me of any changes that might have occurred in FF 36.0.2 or higher that would have changed the way FF interacts with proxy services and security settings? I'd like to track down the change so that I can start to determine the best way to fix the issue.
Thank you! Ben
Wszystkie odpowiedzi (5)
You can try to disable IPv6 (check for other possible causes as well).
Thanks for the quick response. I tried disabling IPv6, that did not seem to effect the issue. I should clarify, the "crashing" described earlier is actually a blocking of communication by our proxy. I attached a screenshot.
Today I tried to change the proxy settings in System Preferences > Network > Advanced > Proxies to "Automatic Proxy Configuration" with the relevant URL, and I tried entering the Proxy config (for HTTP, HTTPS, and FTP manually), both with and without the saved user authentication credentials. None of it made a difference.
I also tried changing the proxy config settings in Firefox > Preferences > Advanced > Network > Settings. Tried Auto Detect Proxy Settings, Use System Proxy Settings, Manual Proxy config, and Automatic Proxy Config URL, again...no improvement.
Again, this behavior has occurred with every update that we've test since 36.0.1. We have 1 user on 10.10.3, and the rest on 10.9.5. The behavior is the same for all users.
Any additional ideas are appreciated.
Did you try "No Proxy" as well?
Do you have security software that might be blocking Firefox?
Does this happen with all pages apart from built-in about: pages?
Create a new profile as a test to check if your current profile is causing the problem.
See "Creating a profile":
- https://support.mozilla.org/kb/profile-manager-create-and-remove-firefox-profiles
- http://kb.mozillazine.org/Standard_diagnostic_-_Firefox#Profile_issues
If the new profile works then you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over problems.
Thanks for the continued help.
1. We did try No proxy, same behavior.
2. This office is using Websense for web content filtering, and an in house proxy.
3. This issue does happen with all web pages except for the built-in about: pages.
Extra context: A. PC's using the same versions of firefox (including the latest versions) on the same network with the same content filtering and proxy settings do not show the behavior.
B. The Macs that do show this behavior with any version after 36.0.1 do not show any error with Safari or Firefox.
This is what leads me to believe that something must have changed in Firefox 36.0.2 and after that caused this failed communication with the proxy server.
I will try the profile tip you recommended and post an update. If you have any other tips, as always, I appreciate the help.
Update - Followed Cor-el's advice and tested with multiple new profiles = no change.
Also tried to create multiple brand new users and test new installs of 39.0 = no change.
I think what I might need is a change log between version 36 and 36.0.1 that highlights any changes that both:
A. Would have any relevance on proxy/security settings B. Stay consistent from 36.0.1 through 39.0
Any further help is very appreciated. We are at a loss. Firefox has been the best browser for our employees for some time specifically because of the way it remembered our proxy settings and remained authenticated, while other browsers constantly ask for our users to reauthenticate with the proxy whenever they visit a new site.
Thank you, Ben