Try Firefox Safe Mode to see if the problem goes away. Safe Mode is a troubleshooting mode, which disables most add-ons.

(If you're not using it, switch to the Default theme.)

• You can open Firefox 4.0+ in Safe Mode by holding the Shift key when you open the Firefox desktop or Start menu shortcut.
• Or open the Help menu and click on the Restart with Add-ons Disabled... menu item while Firefox is running.

Once you get the pop-up, just select "'Start in Safe Mode"

If the issue is not present in Firefox Safe Mode, your problem is probably caused by an extension, and you need to figure out which one. Please follow the Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems article for that.

To exit the Firefox Safe Mode, just close Firefox and wait a few seconds before opening Firefox for normal use again.

Please report back soon.

I tried running Firefox in Safe Mode last night and didn't have any crashes. I will try to run it in Safe Mode for a longer time soon and see if anything happens. I will post with an update once I have done that.

please run a full scan of your system with different security tools like the free version of malwarebytes and adwcleaner.

in case you have trusteer rapport installed on your pc, please update it to the latest version available since it is also known to cause the exact same type of crashes as you're experiencing.

I also installed firefox 24.0 on windows 8 . While I was looking for solutions on how to speed up firefox, I unchecked the "Use hardware acceleration when available" option. When restarted and logged in linkedin and facebook, the system hangs. Now I am restarting the system windows 8 and its taking a century to reboot , although windows 8 is updated and there is no plugin in firefox , every plugin/addon is disabled. Firefox 24.0 crashes especially when I log into Linkedin and facebook.

hello fahad19, your problem is sounding quite different from that of the topic owner - please open a new question for your issue and include the troubleshooting information and the latest few crash ids - this will make troubleshooting your issue & hopefully finding a solution much easier!
thank you

ok I'll open a new thread. Just for the record, I restarted firefox in safe mode with all plugins disabled and checked back the "Use hardware acceleration" , and when i opened the linked in and facebook login pages, the same thing happened. Now restarting windows 8 again . This is very painful .

If no crashes are occurring in Firefox's Safe Mode, than the issue is caused by an add-on, plugin, theme or Firefox setting.

You can try trail-and-error for troubleshooting add-ons. Just disable one extension and restart Firefox. If that one doesn't fix the issue, enable it and try another add-on.

Please make sure that all of your plugins are up-to-date. This can be done by using the Mozilla Plugin Check.

Please report back soon.

In Firefox Safe mode these changes are effective:

• all extensions are disabled
• default theme is used (no persona)
• userChrome.css and userContent.css are ignored
• default toolbar layout is used (localstore-safe.rdf)
• Javascript JIT compilers are disabled (javascript.options.*jit)
• hardware acceleration is disabled

• plugins are not affected
• preferences are not affected

Hi , I think i am having a problem with windows 8, the same thing happened with IE and chrome . I have tried the safe mode option as well, still the same things happen. all plugins are disabled and when Linkedin or Facebook login page appears it just hangs the entire system.

I tried updating windows 8 but now its reverting the changes. If it reverts the changes i'll give a try to nightly and check but this is going really painful with windows 8. If this keeps happening, i'll just install windows 7 again.

@ fahad19

If you have tried all of the above steps and still haven't solved the issue, please consider creating a new thread with the specifics of your issue. This will ensure that you will receive customized and accurate support based upon your issue.

I am trying Firefox in Safe Mode today so we'll see if I have any crashes. I haven't had as frequent of crashes the past couple days as when I first downloaded 24.0 but I am still getting daily crashes. The crashes usually occur when I am using Google Images or Google Maps. However, I have left Firefox open with just a few tabs up and been away from the computer for a few hours and come back to a crashed Firefox.

Here are the crash reports from today and yesterday:

bp-673d67eb-0804-4ec2-b743-44b892130921 bp-e2cb82ac-e0f6-4568-9eef-7e5362130921 bp-293fa4f6-8631-4b1f-bd59-ff6fa2130920

Please start your own thread then post back here to confirm you have done that. That makes it much easier to give you the correct advice, and anyone who wishes may follow your progress.

Please

1. Use this special quick direct link to start your own thread.
2. Follow the prompts to include full troubleshooting information when you write the question
3. In the new thread
   • Say whether you still get crashes in Firefox's safemode
   • see Diagnose Firefox issues using Troubleshoot Mode
   • If you do get crashes please post the new Crash IDs
   • Also say whether you use any Norton software or Trusteer Rapport.

Firefox did not crash while it was in Safe Mode.

Deserin, Apologies, this is your own thread!

You have already tried turning off JS compilers and hardware acceleration, but are crash free in Firefox's safe mode. It is probably some extension or toolbar,and in fact we know from other threads that Norton related software has been causing Firefox 24 crashes and you have Norton software per your system information aside.

Sorry I missed that. It will almost certainly be he cause of your crashes. Note the core Norton AV software will continue to function and protect your system. Disable the other Norton Software. Note also that Norton usually synchronises update with Firefox Releases and so it is usually expected that the software only needs updating.

At present there is a known problem see

• see https://community.norton.com/t5/Norton-Toolbar-Norton-Identity/Firefox-24-still-crashes-when-the-NIS-toolbar-is-enabled/td-p/1023987
  • note also that site has a mixed content issue with Google Chrome and now Firefox. Click on the shield Icon and make it an exception to see the site properly. ( That is also a known issue that Norton must be aware of Bug 905183 )

Since Firefox didn't crash while in Safe Mode, it is an add-on causing the issue.

Use trial and error to figure out which add-on is causing the issue.

1. Disable an add-on
2. Restart Firefox
3. If the issue occurs, enable the disabled add-on then restart from step 1

Please report back soon.

Disabling the Norton toolbar did the trick. Thanks everyone!

Glad we helped & that it is working. Thanks for posting back.

I see on the Norton forum thread has now reached 9 pages but it is getting attention from their developers and there is mention of news soon, with a fix being tested.

• https://community.norton.com/t5/Norton-Toolbar-Norton-Identity/Firefox-24-still-crashes-when-the-NIS-toolbar-is-enabled/m-p/1027739#M14000

For forum cross referencing purposes

• Some of your Reports for Crash IDs
  1. bp-0e9e5bd4-1f9b-4e61-88d0-c940021309194
     bp-e4a92dc8-5bc0-479e-9b96-9ee072130919 &
     bp-0f1b04ae-b6b1-4058-9558-a7ef32130918
  2. bp-886eb5d0-cf86-412b-a1f6-747282130919 &
     bp-1c984e4c-6556-4294-9a0f-fa53f2130918
  3. bp-673d67eb-0804-4ec2-b743-44b892130921
• Crash signatures
  1. js::GCMarker::processMarkStackTop(js::SliceBudget&)
  2. ScanRope
  3. XPC_WN_NoHelper_Trace
• Includes related bugs
  1. Bug 719114 - Firefox Crash @ js::GCMarker::processMarkStackTop
     Bug 817342 !
  2. Bug 668583 NEW --- crash @ js::gc::ScanRope
  3. Bug 752845 NEW --- Crash in XPC_WN_NoHelper_Trace

There are other threads where Norton software is involved, and possibly additional crash signatures. ( edit includes thread /questions/971603 )

Hi guys

Good it got fixed, a little note on Firefox not working in safe mode is add-on related. My FireFox did crash over and over, and in my case it did not always work in safe mode either. After several days testing, it seems to be one or more of the Updates in Windows Update as of late the makes this happen. Simply uninstalling those fixed the problem.