Firefox crashes
Everyday since updating to 33.0.2, I get crash report window when I x out of firefox homepage. This has been happening several times a day. I have 2 issues that keep showing up. They are 987323 and 1057312. I keep sending the error reports back to you. The only comments I have seen from you when I click on either of these issues are dated from the 26th of last month and I think the other issue is dated from the beginning of October. I updated Firefox on the 29th I think. Help! I am tired of seeing the crash report window all the time!
Chosen solution
You may have to wait till next week when Firefox 33.1 will be released and for now make sure that you have the latest Avast updates.
- bug 1087674 - Firefox won't close with Avast 2015 10.0.2206 when HTTPS scanning is enabled
All Replies (10)
Hey there,
We're sorry to hear that Firefox is crashing. In order to assist you better, please follow the steps below to provide us crash IDs to help us learn more about your crash.
- Enter about:crashes in the Firefox address bar and press Enter. A Submitted Crash Reports list will appear, similar to the one shown below.
- Copy the 5 most recent Report IDs that start with bp- and then go back to your forum question and paste that into the "Post a Reply" box. (Please don't take a screenshot of your crashes, just copy and paste the ID's. The below image is just an example of what your Firefox screen should look like)
Thanks for the help!
Curtis Parfitt-Ford Mozilla Support
bp-da06bc5c-c9ac-4477-9063-6d1f62141101 11/1/2014 7:02 AM bp-239ea29c-3046-4798-927f-725a32141101 11/1/2014 6:37 AM bp-34af4e45-2912-4c56-9da3-60bb02141101 11/1/2014 6:32 AM bp-789e380a-63dc-4245-969d-92d3b2141101 10/31/2014 9:05 PM bp-7705332d-ee7e-430d-b98c-427aa2141101 10/31/2014 8:56 PM
Hey there,
Do you use Avast! Antivirus by any chance?
Thanks!
Curtis Parfitt-Ford Mozilla Support
Yes I use Avast 2015.10.0.2206. However, the issue with Avast showed it was resolved on your end when I looked at my crash reports. The number of that issue was 1087674 re: "Firefox won't close with Avast 2015.10.0.2206 when HTTPS scanning is enabled".
Some added toolbar and anti-virus add-ons are known to cause Firefox issues. Disable All of them.
These programs were flagged in the crash report;
mbae.dll = Malwarebytes Anti-Exploit
KERNELBASE.dll = Microsoft Corporation
ntdll.dll = Microsoft
Perform a System File Check to fix the corrupted system files http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html
Chosen Solution
You may have to wait till next week when Firefox 33.1 will be released and for now make sure that you have the latest Avast updates.
- bug 1087674 - Firefox won't close with Avast 2015 10.0.2206 when HTTPS scanning is enabled
Had 2 crash reports today and 1 yesterday for the same 2 bug numbers 1057312 and 987323. Above issue bug 1087674 has been resolved so I am not sure why you responded with that issue as a solution. My Avast is up to date. Will the new Firefox 33.1 take care of these 2 issues that just keep hanging on? Also I don't get the crashes every time a close Firefox. Why is this? I keep going to the same sites I usually do (email, weather, etc.). Also you replied that Malwarebytes Anti-exploit could be a problem, but it hadn't been an issue with Firefox before I updated Firefox. I don't know what the Kernalbase.dll and ntdll.dll are.
Here are the last 5 crash reports submitted. bp-741ecc4a-9fc9-4183-a21d-2a5872141103 11/3/2014 3:36 PM bp-ba95af4c-03a3-4dd6-a4d5-17a942141103 11/3/2014 3:20 PM bp-dba9fcfa-bf1d-4d9e-91f0-7df8d2141103 11/3/2014 1:20 PM bp-b4171b3f-8ae7-4c0e-8b93-1d1032141102 11/2/2014 10:15 AM bp-babff520-3ecb-45a1-9668-6c3e62141101 11/1/2014 10:44 AM bp-da06bc5c-c9ac-4477-9063-6d1f62141101 11/1/2014 7:02 AM
bug 1087674 is still present in Firefox 33.0.2 although it is possibly fixed by Avast if you have updated Avast with the latest fixes. Only the Firefox 33.1 release (scheduled for next Monday) will have this bug fix.
Boot the computer in Windows Safe mode with network support (press F8 on the boot screen) as a test to see if that helps.