Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Mulongo oyo etiyamaki na archive. Tuna motuna mosusu soki osengeli na lisalisi

Firefox crashes

  • 6 biyano
  • 3 eza na bankokoso oyo
  • 2 views
  • Eyano yasuka ya MMBrown26

more options

For many months I have experienced Firefox crashing. I have tried going into Firefox Safe Mode and, one by one, Checking operation with extensions and plugins, hoping to find what is wrong. It still crashes. I have uninstalled and reinstalled. No luck so far. Any help you would provide is greatly appreciated! Thank you!

For many months I have experienced Firefox crashing. I have tried going into Firefox Safe Mode and, one by one, Checking operation with extensions and plugins, hoping to find what is wrong. It still crashes. I have uninstalled and reinstalled. No luck so far. Any help you would provide is greatly appreciated! Thank you!

All Replies (6)

more options

hello, could you provide your latest few submitted crash reports? please enter about:crashes into the location bar, copy the latest few report ids from there starting with bp- & paste them here into a forum reply. this will give us a better understanding what may be triggering those crashes.

more options

Yes, here are the Report ID's. And thank you!!!

Report ID Date Submitted bp-d52d837f-1072-4d58-8dd2-89e932161115 11/15/2016 8:25 AM bp-dbe01e19-d7bf-48e1-9383-e89722161114 11/14/2016 8:01 AM bp-234f716a-bb16-48ed-b66c-fa02a2161112 11/12/2016 10:21 AM bp-e7b05e60-0bd0-43af-b953-8261d2161111 11/11/2016 1:57 PM bp-7be573ca-f1af-423b-935c-e18a02161111 11/11/2016 8:15 AM bp-da68e105-3e61-44ae-af33-eb5862161110 11/10/2016 5:39 PM

more options

thanks, they appear to be caused by different factors and aren't all the same.

what i'd propose first is to uninstall firefox and switch to a 64bit version of the browser (which should get rid of the out-of-memory type crash signatures): https://download.mozilla.org/?product=firefox-latest&os=win64&lang=en-US - your data & customizations won't be affected by this and remain after you've installed the 64bit build.

one other issue (crash signature nsXPCWrappedJS::nsXPCWrappedJS) seems to be partly related to kaspersky - some other users have reported that an upgrade to the kaspersky 2017 product line (https://usa.kaspersky.com/downloads/software-upgrades/) might address the problem. we are also in contact with kaspersky about this and in order to better understand the problem, they are looking to access a full crash dump from an affected user. as this may contain personal information (like the visited websites during the session of the crash), we would not hand that over to a third-party without prior consent of a user. would you be OK with letting Kaspersky access your crash dump? if so please let me know as this would be of great help and may benefit many other Firefox users as well!

finally, if those steps didn't reduce all crashes, i'd also recommend to test the integrity of your hardware/ram with a tool like memtest.org...

more options

I removed Kaspersky 2016. I uninstalled the prior version of Firefox. Then rebooted system. New 64-bit version of Firefox is installed. I then installed 2017 current version of Kaspersky. When first starting Firefox afterwards Kaspersky add-on protection requested installation. I agreed to it. This add-on I have noticed does slow connection speeds to websites at the benefit of possible protection(?). I have many times considered removal of that feature to see what would happen. Do you know how safe a move that is? I did read on the web reports of many users of Firefox (I use it exclusively) having issues with the Kaspersky protection add-on to Firefox. Many have told me personally that it slows down speed of access to websites as every file is scanned before a site will appear.

I would like to see how the changes made so far go.

If a crash dump were to be provided to Kaspersky do you need me to send one to you? I would still prefer to wait until I can see how the changes made so far affect the crashes I have been experiencing for almost a full year. But I will consider providing a crash dump that you could give to Kaspersky in order to help other users.

Or do you already have the crash dump info?

Thank you!

more options

yes, we would already have the crash dump information linked to your crash report bp-7be573ca-f1af-423b-935c-e18a02161111 - by default this is secured so that only a handful of mozilla engineers working at fixing stability issues have access to them, but in this case kaspersky would have requested to analyse one of those kind of crashes as well, because without that information they are a bit in the dark of what part of their program might trigger the problem.

in regards to the protection addon - as long as you stay alert and are careful which files you download/execute i don't think that such addons add much benefit... (personally i'm not using any of them at least)

more options

I am very careful what I allow to download, etc. So I will turn off the Kaspersky plug-in scanning add-on function in Firefox as well. FYI, I just completed memory testing with Memtest with no errors on any test resulting. Let me see how things go after making the above changes and get back with you either way by mid-December if you could wait that long to let me test how the present changes go. I am not keen on handing over to Kaspersky any private information but would consider doing so if the present changes do not work. Thank you.