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

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

Firefox keeps crashing when I'm on Facebook....while reading posts on my page....playing a game. Can someone tell me why?

  • 5 uphendule
  • 5 zinale nkinga
  • 1 view
  • Igcine ukuphendulwa ngu LadyLayne

more options

I keep getting the pop-up box that (Mozilla/Firefox?) has crashed when I am on Facebook. It happens when I'm on my page reading posts, posting, and/or playing games.

The info in the box says the url is included in the report; ask for any info I can give; states someone might contact me via email.

This has been happening with more and more frequency the past couple of months.

Is there anything I can do to correct whatever the problem is?

I keep getting the pop-up box that (Mozilla/Firefox?) has crashed when I am on Facebook. It happens when I'm on my page reading posts, posting, and/or playing games. The info in the box says the url is included in the report; ask for any info I can give; states someone might contact me via email. This has been happening with more and more frequency the past couple of months. Is there anything I can do to correct whatever the problem is?

All Replies (5)

more options

Thank you for submitting crash reports. They are compiled for consideration by developers, but in order to share them with forum volunteers, we need to get the links from you.

Please check the last section of our support article "Firefox Crashes" for steps to get those crash report IDs, and then post some of the recent ones here.

more options

Here are some of the most recent crash reports:

bp-ed66b282-ab23-470f-9953-a46472141113 11/13/2014 5:19 PM bp-a2b6e4e3-5370-41e3-834a-139292141113 11/13/2014 4:15 PM bp-800e2f1e-f2cc-4cba-98be-3baec2141111 11/11/2014 6:45 PM 48ebd946-16c7-4bc5-b521-f6094d096b24 11/11/2014 6:33 PM bp-5f72f5ca-8b46-4da5-bf7c-7d56d2141111 11/10/2014 10:00 PM bp-53cc081d-ee5d-4010-a81e-e36422141111 11/10/2014 7:20 PM fb71b360-2b22-4205-a5ed-a6558d5cfd4a 11/10/2014 12:50 PM b3d46468-a112-4909-acca-054195a4f51a 11/9/2014 1:19 AM bp-e5760054-e74f-489f-bbb9-2b7a92141107 11/6/2014 11:24 PM bp-70c4ddc2-2162-4581-98b1-58d7e2141106 11/5/2014 7:22 PM bp-b39082a6-8736-4078-af54-89f3c2141106 11/5/2014 7:22 PM bp-035a3e6b-2ef5-482c-8a5d-aaeea2141105 11/5/2014 2:27 PM bp-2eaa2314-ea3b-440f-8955-cc3712141102 11/2/2014 5:26 PM bp-eb8e8e48-f43b-4a78-998f-0527c2141102 11/1/2014 8:11 PM 8a014ebd-d840-494f-aaff-cc14590f2751 11/1/2014 5:39 PM bp-8ed6e06f-87b9-41ed-aa6d-41fa92141101 11/1/2014 7:04 AM 52f61921-2983-4a22-a70c-6ff385a6d39f

Hope this info is helpful LL

more options

jscher2000's reply let me know someone is really monitoring support for new questions. I really appreciate the prompt reply.

LL

more options

Hi LadyLayne, thank you for the crash report IDs.

The newest one has been reported about 900 times in the past 28 days, with only one comment indicating what the user was doing (working in AOL email, not on FB in that case). It is linked to an old bug in the tracking system, and its cause/solution is not obvious to me. Because system memory use was at 90%, it's possible that Firefox stepped on itself somehow trying to manage memory, but I don't think there's any way to know for sure.

The next one is more common, with over 6,000 reports in the past 7 days. Many user comments relate it to use a plugin, probably the Flash player plugin. On the FB news feed, I think Flash is used extensively, so that could be relevant. This suggests that one possible workaround could be to keep Flash disabled on a site until you are sure you need it. I'll describe that option in more detail further below. There is a bug in the tracking system related to this which is focused on a background activity called garbage collection which involves cleaning up memory. That doesn't immediately suggest any workarounds for you.

The third and fifth ones are crashes in Firefox's "Baseline" JavaScript compiler. Firefox uses compilers to speed up scripts, but this process can sometimes lead to errors. You could try disabling the compiler to see whether it helps. Since these "EnterBaseline" crashes are probably intermittent, it might take a while to notice any difference. I'll list the steps for that below.

The fourth crash is not linked.

The sixth crash also is related to the JavaScript compiler feature.


Setting the Flash plugin to Click-to-Play ("Ask to Activate")

Open the Add-ons page using either:

  • Ctrl+Shift+a
  • "3-bar" menu button (or Tools menu) > Add-ons

In the left column, click Plugins. Look for "Shockwave Flash" and change "Always Activate" to "Ask to Activate".

When you visit a site that wants to use the Flash, you should see a notification icon in the address bar and one of the following: a link in a black rectangle in the page or an infobar sliding down between the toolbar area and the page. You can approve Flash to run when you're ready.


Disabling the Baseline Compiler

(1) In a new tab, type or paste about:config in the address bar and press Enter. Click the button promising to be careful.

(2) In the search box above the list, type or paste javas and pause while the list is filtered

(3) Double-click the javascript.options.baselinejit preference to switch it from true to false. I'm not sure whether that takes effect immediately or the next time you exit and start Firefox up again.

Notice any difference?

more options

I haven't had any problems since I submitted my question. I have saved your reply with instructions for what to do, in case I should have problems in the future. I did check under Add ons and changed plug-in to "Ask to activate". Thank you very much for your help.

LL