This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

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, exception_stack_overflow?

  • 13 biyano
  • 2 eza na bankokoso oyo
  • 12 views
  • Eyano yasuka ya Clol7

more options

Problems with either

A. Other programs unfocusing to firefox

B. Firefox unfocusing, even if it's the only program open.

It always crashes after one of these. I did send a crash report, is there any way I can help speed it along?

Problems with either A. Other programs unfocusing to firefox B. Firefox unfocusing, even if it's the only program open. It always crashes after one of these. I did send a crash report, is there any way I can help speed it along?

Solution eye eponami

Well, I have had a stroke of genius, and identified the issue myself.

It was a bugged (or broken) extension, designed to force youtube to use the flash player rather than the HTML5 player, as the HTML5 player was bugged itself at the time.

Disabling it did the trick.

Tanga eyano oyo ndenge esengeli 👍 0

All Replies (13)

more options

I did forget to say, that this has started since 38.0.1

more options

Thank you for submitting your crash report(s). Those go into a database for triaging and prioritization, but for personal assistance, it would be great if you could post your crash report ID(s) here. You can find those on the about:crashes page as described in the last section of the support article "Firefox Crashes".

If Firefox won't stay "up" long enough to copy the list, have you tried Firefox's Safe Mode? That's a standard diagnostic tool to bypass interference by extensions (and some custom settings). More info: Diagnose Firefox issues using Troubleshoot Mode.

If Firefox is not running: Hold down the Shift key when starting Firefox.

If Firefox is running: You can restart Firefox in Safe Mode using either:

  • "3-bar" menu button > "?" button > Restart with Add-ons Disabled
  • Help menu > Restart with Add-ons Disabled

and OK the restart.

Both scenarios: A small dialog should appear. Click "Start in Safe Mode" (not Refresh).

more options

While you are troubleshooting this, it might be helpful, to avoid unnecessary pain on sites where Flash is not actually essential, try setting Flash to Click-to-Play ("Ask to Activate"). This will delay Flash from starting on a page until you approve it.

To set "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 ignore the notifications if Flash is not important for that site.

Not a solution, but hopefully will help a bit.

more options

Okay. Assuming the crash ID is the UUID in the report, it'll be this:

927fc6ea-6ed7-4b60-964c-bf58f2150519

more options

Hmm, there isn't much info available about this crash signature:

nsStreamListenerWrapper::OnStartRequest(nsIRequest*, nsISupports*)

In the report, the crashing thread lists this function over 100 times in a row. That doesn't seem normal to me, but I don't know what page or process needs to open so many connections.

Can you associate it with any particular page or kind of content?

Did you have any better results in Firefox's Safe Mode?

more options

No, not really, but I have gotten better results by clearing the cache and cookies, I haven't yet gotten a crash, but I'll keep you posted.

more options

It seems to have stopped the crashes, but the window still loses focus, and occasionally flashes on the taskbar.

more options

When Firefox loses focus, is there only one Firefox window?

There was (is?) an old bug in the Flash plugin where initiation of protected mode could cause focus to change between windows. The protected mode feature of the Flash player plugin has security benefits, but seems to have compatibility issues on some systems. There is a hidden setting to disable it if you want to try it:

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

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

(C) Double-click the dom.ipc.plugins.flash.disable-protected-mode preference to switch its value from false to true.

This might not take effect until all Flash has been unloaded for a few minutes, or you close Firefox.

more options

No, there's only one firefox window.

more options

You can try to disable McAfee SiteAdvisor.


Do a malware check with several malware scanning programs on the Windows computer. Please scan with all programs because each program detects different malware. All these programs have free versions.

Make sure that you update each program to get the latest version of their databases before doing a scan.

You can also do a check for a rootkit infection with TDSSKiller.

See also:

Ezalaki modifié na cor-el

more options

Solution eye oponami

Well, I have had a stroke of genius, and identified the issue myself.

It was a bugged (or broken) extension, designed to force youtube to use the flash player rather than the HTML5 player, as the HTML5 player was bugged itself at the time.

Disabling it did the trick.

more options

Aha! There are a couple of extensions for that, so if one doesn't work any more, you could try the other.

Or if you no longer need it, disabling or removing is good.

more options

Well that first one there, is the one that caused the problem in the first place, but the HTML5 player is working now, so I won't need it. Thanks for the help though.