Este fío arquivouse. Faga unha nova pregunta se precisa axuda.
Does 38.0.1 have a problem with crashes? I read that 38.0.0 had a problem, which was fixed by 38.0.1, but crashes have been really bad since 38.0.1 update.
I've been crashing about every minute after restart, sometimes sooner, since 38.0.1 update. I think it's triggered by opening a new tab, or navigating to a new page, but not any site in particular.
Thanks! I think I've fixed the problem by doing a Refresh. I wonder whether I had a add-on that wasn't compatible with the new version, or whether the update did something bad to my profile.Ler a resposta no contexto 👍 0
All Replies (14)
Uninstalling and reinstalling has not fixed the problem. Firefox crashes as soon as I try to open a new page, even with a completely new session.
Could you test in Firefox's Safe Mode? That's a standard diagnostic tool to deactivate extensions and some advanced features of Firefox. More info: Diagnose Firefox issues using Troubleshoot Mode.
If Firefox is not running: Hold down the Shift key when starting Firefox.
If Firefox is running: You can restart Firefox in Safe Mode using either:
- "3-bar" menu button > "?" button > Restart with Add-ons Disabled
- Help menu > Restart with Add-ons Disabled
and OK the restart.
Both scenarios: A small dialog should appear. Click "Start in Safe Mode" (not Refresh).
Any less crashy?
When Firefox crashes, it often records information about what was happening at that moment. You often will see the Mozilla Crash Reporter dialog come up. You can submit that data to Mozilla and share it with forum volunteers to see whether it points to the solution. Please check the last section of the support article "Firefox Crashes" for steps to get those crash IDs, and then post some of the recent ones here.
Thanks! I think I've fixed the problem by doing a Refresh. I wonder whether I had a add-on that wasn't compatible with the new version, or whether the update did something bad to my profile.
I think I've traced the problem to the NoScript extension. With that extension enabled Firefox crashes on almost every page navigation. With it disabled (and other extensions enabled), I'm not having crashes.
So I guess I'll wait for NoScript to be updated. This is pretty puzzling though, because I would have expected a Firefox update to be tested with such a popular add-on.
Wow, that's really unfortunate. I can think of one feature of NoScript that might be the culprit, which is audio notification of blocked scripts. You can try editing a preference in about:config (while Firefox is running) or the prefs.js file (while Firefox is not running) to disable that feature if you can't access the NoScript dialog. Then if you reinstall NoScript, that setting should be in effect.
The preference to be set to false is as follows (editing one edits the other):
- Using about:config => noscript.notify
- In prefs.js => user_pref("noscript.notify", false);
I couldn't find that preference I'm afraid (but thanks!).
But looking at my crash reports suggests that in fact the root cause of the problem is not NoScript but rather something called Trusteer Rapport End-point Protection (which is online banking security software). It seems that since the 38.0.1 update, there is an interaction between Trusteer and NoScript which results in crashes in rookscom.dll which is a Trusteer dll.
STR: install Firefox 38.0.1, NoScript and Trusteer Rapport, then start Firefox and navigate a little. I always crash within a minute. Disabling either Trusteer or NoScript gets rid of the crashes.
I'm reporting this issue to Trusteer, because presumably it is their bug. But if others can reproduce this it might be a good idea for Mozilla to add a release note, and contact Trusteer themselves.
I haven't heard about a new issue with Firefox 38... IBM/Trusteer released an update around May 6th to solve a crashing problem with Firefox 37.0.2. This thread has links to try to get the update if the software hasn't updated itself to at least that version by now: https://support.mozilla.org/questions/1061312
I see you also posted on noscript.net forums, so hopefully they will spot the issue if it's something that needs to be fixed in Firefox. (The odds they will spot it are much better than me spotting it!)
Yes I did, thanks for all your help. The latest version of Trusteer doesn't fix the problem, but hopefully they will sort it out reasonably quickly.
I was having short freezes every few seconds while trying to type posts like this one. Disabling the OpenH264 plugin seems to have resolved it. Any known issues like this?
I reinstalled 38.0.1 thinking the original install was bad. I had downloaded 38.0 before it was officially released. Crashes continue. I have Noscript and IBM's Trusteer Rapport.
I have Noscript and IBM's Trusteer Rapport.
Apparently Firefox 38 + NoScript + Trusteer Rapport is crashy. For now, I think one of those needs to not be running, and it may be that for most of your daily browsing, Rapport is the one to disable.
Got the exact problem since v 37.0.2 responding very slowly lots of delay to response any action and a lot of crashes !!
I have sent a lot of reports when FF windows crashes and there was not a single response !
I don't have to run FF in same mode as it suppose to act as it is in a normal way with all add ons on I haven't added any add ons
and it was operating pretty good before V v 37.0.2 So the problem isn't from add ons as it appeared right after updating FF to newer version the upgrades seems to be damages the browser rather than fixing it
I have read a lot of complain about that FF crashes and how it operates very slowly in the past months now this must end
Please fix that I don't want to switch to another browser !!
Hi q8marronglace, could you start a new question with a list of your most recent crash report IDs? This thread is already marked solved so your post is likely to get lost here.
You can start your new question here: https://support.mozilla.org/questions/new/desktop/fix-problems
The last section of this support article describes how to use the about:crashes page to get the crash report IDs: Troubleshoot Firefox crashes (closing or quitting unexpectedly)
Also, you are in the right place for personal assistance with your crashes now. The crash reports you submitted are analyzed for prioritization and triage, but the bug trackers rarely contact you about them unless they need your help tracking down the cause.