How can I stop the "Firefox has stopped working" window from appearing?
Sometimes Firefox actually stops working and "pop-up" window appears with the message "Firefox has stopped working". I have a process that continually monitors FF which is running a GM script 24/7 and when it spots that FF has stopped working it aborts the process and restarts FF. Unfortunately the pop-up window doesn't go away and the old process is still seen in the mix. If I manually click on the stop program button in the window then the new FF process also seems to die. If I close the window using the X button then I have a FF ghost process that won't stop. How can I stop the window from appearing?
Windows 7 FF 30.0 GM 2.0
All Replies (19)
Hi Help Desk, thanks for response. I'm not able to test it with a local profile. I don't have the admin. rights to install anything on the local drive, also I can't modify the Registry.
I would love to post the crash reports if I could find out how to do that, they don't get automatically posted and I can't find a procedure to post the ones listed in about:crashes. Maybe you can explain to me how to do that.
Just in case it could be involved. A couple of thoughts partly because I am not sure which versions of Firefox or Firefox ESR you may be using and I guess CAPS changes could be an issue capable of causing crashes.
- Did this problem occur after a version change in Firefox ?
- What version of Firefox or Firefox ESR are you using ?
- It may be worth testing and comparing Fx24.6 ESR, Fx29, Fx31
- Note change then partial u-turn in implementation of Configurable Security Policies (CAPS) https://developer.mozilla.org/en-US/Firefox/Releases/29/Site_Compatibility#Security
Per-domain Configurable Security Policies are no longer available Bug 913734 – Remove domain policy goop from CAPS Bug 995943 – local (file://) links don't work even when configured for company's internal system Bug 1004260 – Firefox 29 broke clipboard access; restore the CAPS allowclipboard policy until the Clipboard API allows click-to-copy
John48, Happy to explain how to do this, Fred's instructions are mentioned here
as well as [Firefox crashes - Troubleshoot, prevent and get help fixing crashes]
Troubleshoot Firefox crashes (closing or quitting unexpectedly) ~J99
If there is no submit you can also read them in this folder: Please see the viewing reports outside of Firefox section. Copying and pasting is helpful. Or you can manually move the report to the "Submitted folder". https://support.mozilla.org/en-US/kb/Mozilla%20Crash%20Reporter#w_viewing...
John99 மூலமாக
I've just had a crash and a dump was submitted. https://crash-stats.mozilla.com/report/index/bp-151013b4-b6c6-4708-8cb6-14d8b2140718
Now if I could just find a way to programmatically detect the crash reporter window and press the restart button. I could solve some of my problems.
Your memory is a bit high, but that's for later.
Total Virtual Memory 2147352576
Available Virtual Memory 1541894144
System Memory Use Percentage 46
Available Page File 5717889024
Available Physical Memory 1989754880
I tried to look up your add-ons but could not see what they are.
Start Firefox in Safe Mode {web link} While you are in safe mode; Press the Alt or F10 key to bring up the tool bar. Followed by;
Windows; Tools > Options Linux; Edit > Preferences Mac; application name > Preferences
Then Advanced > General. Look for and turn off Use Hardware Acceleration.
Poke around safe web sites. Are there any problems?. Then restart.
Hey John48, Just wanted to follow up with you to see how it was going. The crash report is a unique signature, but it is crashing in the module:
msvcp100.dll
Which is related to part of Visual C++ redistributable. I am not sure how to check if this is updated but is it up to date? http://support.microsoft.com/kb/2019667
Hi, Add-ons are Console2 0.9 Greasemonkey 2.0 HTML Validator 0.9.5.8
I never use this copy of FF for any web sites other than the one that give the crashes. I'm pretty convinced that it's the JavaScript in the web sites pages that are causing the crashes. The system has run non-stop since Friday without a crash. I've switched off hardware acceleration to see if it makes any difference but it might take a week before I know what the effect is because I can't force a crash they just happen at random.
As far as I can tell by googling it's the latest version sfc didn't find any errors.
System File Checker, gotcha. It may be also possible to block specific scripts with Ad Block Plus, but this may just be a temporary work around.
The latest version does come out today as well.
Yes, thanks, but as I said at the beginning, I only use this copy of FF to access one in-house web site using one GM script and so I don't need Ad Block Plus, I never access other websites. If I block javascript then the web site won't work.
I should have waited for your results to for Safe Mode, I am going to take a step back here. FredMcD I believe is the expert here.
Switching off Hardware acceleration did not stop the problem which occurred sometime last night. In the first screenshot you can see the error message and task manager, in the second you can see that FF is running (this is a new copy that was auto-started by my monitor process when it detected that the GM script was no longer producing output)
I found this. Don't know if it will help.
http://www.smartfixer.org/?kw=msvcp100-dll
Windows Msvcp100 Dll Error is caused by misconfigured system files.
So, from my experience, If you got Msvcp100 Dll then there is a 96% chance that your computer has registry problems.
http://www.youtube.com/watch?v=B7tjhJJyWqc MSVCP100 Dll Error Fix - YouTube
The system was very stable for a week or so and then suddenly at the weekend it FF started crashing again on a regular basis. I upgraded to FF 31 yesterday but the problem is still there. I'm really at a loss to find an explanation because nothing changed that I have control over between Wednesday and Monday. (I was on vacation Thursday & Friday and nobody has access to my machine or the software that I'm responsible for except me).
Hi John48, Do you have some of the newer crash reports? Let's check to make sure it is not the same issue and we can investigate from there.
I look forward to your reply!
Well it hasn't crashed for the past 2 weeks. This leads me to believe that the problem is with the network and/or the javascript on the pages that I am accessing.
I checked the crash report again, and it finished. The signature looks like it was trying to allocate a string and there was an error in the webpage.
For troubleshooting javascript in the page that causes it to crash next time we can use the Web Console. I am happy to hear that it has stopped crashing.