> #11 nsAutoScriptBlocker::~nsAutoScriptBlocker() (this=0x7fffffff1c88, _in_chrg=) at /home/mstange/code/mozilla-central/dom/base/nsContentUtils.h:2419 > #10 nsContentUtils::RemoveScriptBlocker() () at /home/mstange/code/mozilla-central/dom/base/nsContentUtils.cpp:5050 > #9 nsHideViewer::Run() (this=0x2aaad15155c0) at /home/mstange/code/mozilla-central/layout/generic/nsSubDocumentFrame.cpp:946 > #8 nsFrameLoader::Hide() (this=0x2aaae7b287a0) at /home/mstange/code/mozilla-central/dom/base/nsFrameLoader.cpp:916 > #7 nsDocShell::SetVisibility(bool) (this=0x2aaadc835000, aVisibility=false) at /home/mstange/code/mozilla-central/docshell/base/nsDocShell.cpp:6354 > #6 nsDocumentViewer::Hide() (this=0x2aaae7df2670) at /home/mstange/code/mozilla-central/layout/base/nsDocumentViewer.cpp:2126 > #5 nsDocumentViewer::DestroyPresShell() (this=0x2aaae7df2670) at /home/mstange/code/mozilla-central/layout/base/nsDocumentViewer.cpp:4430 > #4 nsCOMPtr::operator=(nsIPresShell*) (this=0x2aaae7df26e0, aRhs=0x0) at. > #3 nsCOMPtr::assign_with_AddRef(nsISupports*) (this=0x2aaae7df26e0, aRawPtr=0x0) at. > #2 nsCOMPtr::assign_assuming_AddRef(nsIPresShell*) (this=0x2aaae7df26e0, aNewPtr=0x0) at. > #1 PresShell::Release() (this=0x2aaad8584800) at /home/mstange/code/mozilla-central/layout/base/nsPresShell.cpp:804 Stack where the presShell gets destroyed: To reset Firefox, click on the Menu button and go to “Question mark icon -> Troubleshooting Information.” In the page that loads, select “Refresh Firefox.We access the presShell after it's been destroyed. By resetting Firefox, a new profile folder is created, but don’t worry – you still have your browser history, bookmarks, cookies, saved passwords and auto-fill. Why is this helpful? Because your information is stored in a profile folder, and sometimes there can be problems with that folder.
![firefox 40.0.3 crash constalty firefox 40.0.3 crash constalty](https://www.virusresearch.org/wp-content/uploads/2017/11/Remove-Search-dailybibleverses-co.jpg)
Resetting Firefox can also be very useful since it gets rid of themes, extensions, site specific preferences and search engines. When it has finished processing everything (Look for the words Your report is being processed), close the report tab. Locate the latest crash under Report ID, right-click and select “Open Link in New Tab.” You should see a tab that will lead you to a page on. You should see a page listing submitted crash reports. You can do this by going into the Firefox location bar, typing about:crashes and tapping on Enter. If you were unable to find a solution, you could always try to get help by using your crash ID. Mozilla suggests that you see the Firefox Hot Topics section to see if you can find a solution to your particular problem there. If Firefox is still not stable even in Safe mode, the theme, hardware acceleration or the extensions are obviously not to blame. What to Do When Firefox Keeps Crashing in Safe Mode You can start Firefox in Safe mode by pressing the “Shift” key while it is starting, or you can click on the “menu button – > Question Mark -> Restart with Add-Ons Disabled, When Firefox stops working, you can also try launching the browser in “Safe Mode” to see if an extension is the problem. Select “Start New Session” and hopefully, Firefox will stop crashing.
#FIREFOX 40.0.3 CRASH CONSTALTY WINDOWS#
If you choose “Restart Firefox,” and the crash happens again, there is a good chance that one of the windows or tabs you have opened is causing the crash. That way they can see if the page you were on might have had something to do with the crash. It’s also a good idea to tell the company what page you were on when the crash occurred. The more information you can provide the better. If you want to see the technical details of the crash, click on “Details.” You can add any further information here if you think that it will help Mozilla fix the issue. If you would like Mozilla to contact you about the crash, remember to click on that option as well. This is a dialog box where you can tell Mozilla what has happened so they can do something about it (hopefully). Using the Mozilla Crash ReporterĪfter Firefox crashes, you should see the Mozilla Crash Reporter.
![firefox 40.0.3 crash constalty firefox 40.0.3 crash constalty](https://user-media-prod-cdn.itsre-sumo.mozilla.net/uploads/images/2018-01-11-09-10-22-f71eee.png)
It’s always a good idea since it will certainly prevent your browser from crashing too often and will keep your browser up to date with the latest features.
![firefox 40.0.3 crash constalty firefox 40.0.3 crash constalty](http://4.bp.blogspot.com/-cMGY-sleT1w/UrZevy1HrqI/AAAAAAAABuk/sm3R7DOXdZ8/s320/QQ图片20131222105918.jpg)
Before you try any of the below tips, make sure to always keep the Firefox browser up to date.