firefox 29.0.1 crashes on windows 7
I have 3 pc's all running firefox, 2*8.1 1*windows 7. Never had a problem before the update to 29.0.1. Works fine on 8.1. Crashes constantly on 7. Have reset. Have uninstalled and reinstalled. Have removed Add on extensions and plug ins, have run in safe mode, have scanned for malware with Eset, malwarebyte and Sophos.
You should have the crash reports as it sends them off after every one. Must be in the fifties by now. Really becoming unworkable now.
Please help because the next step is to move to another browser.
Solução escolhida
Deactivating the baseline compiler by going to about:config and changing
- javascript.options.baselinejit.chrome
- javascript.options.baselinejit.content
- in FF 30, the option might be just javascript.options.baselinejit
to false might resolve this problem
Ler esta resposta no contexto 👍 2Todas as respostas (8)
I am having the same problems over my 4 different machines at home and at work. The consist of a mid-range Win7Home desktop, a high spec Win7Pro desktop, an old dual core Win7Pro Laptop and an extremely high spec Win8Pro Laptop.
Not only that, but every person in my office is having the same issues on 100% of their home and work computers. There literally isn't a single one of our 6 office staff that has a working version of FF.29... and that's over 12 different windows setups which even includes a machine running WinXP.
We have ALL downgraded to FF.28 and disabled auto updates, which has got rid of ALL issues for every person involved. It's abundantly clear to all of us that FF.29 is the problem. Unfortunately, we will soon be forced (reluctantly) to change browsers.
As with Naughtyb, Mozilla should have around 200 error reports from our staff alone, as when using a Silverstripe 3 CMS backend, Firefox crashes every 10-30 seconds. (our main php development platform)
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.
Thank you for your help!
More information and further troubleshooting steps can be found in the Troubleshoot Firefox crashes (closing or quitting unexpectedly) article.
bp-6ecfb9b4-759d-4ae8-91ef-0c4342140523 23/05/2014 14:09 bp-3d85573e-74ff-4dc9-a03e-09e162140523 23/05/2014 14:09 bp-e02d491e-5d8c-42d2-9788-898982140523 23/05/2014 14:08 bp-d8ecb93c-b06a-40c4-815c-145642140523 23/05/2014 08:51 bp-a2cd9a16-016a-485b-b0e6-bbe012140523 23/05/2014 08:50 bp-e8155a32-41bb-49d0-a810-4c5f22140523 23/05/2014 08:48
Naughtyb:
Odd but your problem seems to lie with the EMET (Enhanced Mitigation Experience Toolkit). Try either updating it or uninstalling it.
Spambanjo
Please create a new thread by going to /questions/new and adding your crash reports from about:crashes
into the Details field.
It's necessary to create a separate thread for your issue as it gives us your configuration and more than likely, your crash reason isn't the same as Naughtyb's crash.
Moses, Thanks for that. I have updated EMET to 4.1 We shall see how that flies. I will let you know. Thanks again.
As a SilverStripe developer by profession I've also been seeing this issue allot since upgrading to 29 (now 30). I've also been hearing this from other members of the SilverStripe community including the other devs at work. Here's my last 5 crashes.
bp-c8bcf3f5-fe18-4b65-95ad-b52482140612 2014-06-12 4:03 PM bp-a7614fd6-06f6-4697-be80-e9e5c2140611 2014-06-11 3:53 PM bp-80702a2e-758f-4932-9971-1e22a2140602 2014-06-02 9:58 AM bp-bdeca07b-c5f0-4506-87e3-2f1b92140613 2014-06-02 9:27 AM bp-03bd3a92-77a5-4c7a-a047-8b7b02140508 2014-05-08 3:29 PM
Modificado por UndefinedOffset a
Solução escolhida
Deactivating the baseline compiler by going to about:config and changing
- javascript.options.baselinejit.chrome
- javascript.options.baselinejit.content
- in FF 30, the option might be just javascript.options.baselinejit
to false might resolve this problem
Modificado por Corneliu a