cancel
Showing results for 
Search instead for 
Did you mean: 

Send plugin crash reports to help Mozilla improve Firefox

This error means that a plugin (like Adobe Flash) has crashed. Simply reloading the page will restart the plugin, and your video (or other content) will be shown again. Before reloading the page you can add a comment to explain how it happened and send a crash report to Mozilla by clicking on Send crash report. These crash reports help us make improvements to Firefox.

Plugin crash notification Fx21

What is a plugin?

A plugin is a piece of software that displays internet content that Firefox is not designed to display. This usually includes video, audio, online games and presentations that are made in patented formats. Plugins are created and distributed by the companies that make those patented formats. Some common plugins are Adobe Flash and Microsoft Silverlight.

What is a crash?

A crash happens when a piece of software abruptly stops working. Plugins sometimes crash for various reasons, and cause Firefox to crash along with it. For more information about Firefox crashes, see Firefox crashes - Troubleshoot, prevent and get help fixing crashes. Some plugins load separately from Firefox, allowing Firefox to stay open if the plugin crashes.

What information is sent in a crash report?

Crash reports only include technical information to help Firefox developers determine what went wrong, and how to fix it. These reports do not include personal information. The information sent in a report includes:

  • what webpage you were on
  • version of Firefox you were using
  • your operating system
  • installed plugins
  • installed extensions
  • and more technical info.

This information is subject to the Firefox Privacy Policy.

How do I keep plugins from crashing?

Many problems with plugins can be solved by updating to the latest version of the plugin. To check if any of your installed plugins are out of date, visit Mozilla's Plugin Check & Updates page. The name of the plugin that crashed can be found in the error message.

Plugin name crash notification Fx21

Where can I get more info about Adobe Flash crashes?

See Adobe Flash plugin has crashed - Prevent it from happening again.

Developing for Flash with Flex?

Breakpoints can trigger Firefox's hang protection. You can disable hang protection by setting the dom.ipc.plugins.timeoutSecs preference to -1. See the Mozilla Developer Network documentation for details.

Customize this article

Firefox

Firefox for Android

Firefox for iOS

Firefox OS

Thunderbird

Version History
Revision #:
3 of 3
Last update:
3 weeks ago
Updated by:
 
Comments

See /forums/knowledge-base-articles/703986 and /forums/knowledge-base-articles/704932 for related discussion about this article.

greasemonkey

The changes made by scoobidiver and myself need reviewed.

They were approved by Michael Verdi.

How to turn off crash reporting: What does this accomplish?

If we are giving this suggestion we should add a warning that unchecking the "Submit crash reports" option will clear the check box in the Mozilla Crash Reporter to "Tell Mozilla about this crash so they can fix it" and will prevent Firefox crash reports from being sent by default. (We ask for crash report IDs in the Firefox crashes - Troubleshoot, prevent and get help fixing crashes article.)

See http://kb.mozillazine.org/Breakpad#Mozilla_Crash_Reporter (Quote) Note: Unchecking the "Submit crash reports" option/preference (e.g., in Firefox Options -> Advanced / General (tab), under "System Defaults") does not turn off the Crash Reporter; it simply toggles the default of the "Tell Mozilla about this crash so they can fix it" check box in the Mozilla Crash Reporter dialog (upon crash). See: Advanced panel - Accessibility, browsing, network, updates, and other advanced settings in Firefox Also: bug 577221#c6 and bug 580592#c4

That's a good point Alice and now that you bring it up, I think the solution is not add to the article but to cut stuff out. In this case we already tell you in the introduction to just reload the page (which doesn't send a crash report about the plugin) and that if you want to send a crash report you can click the link before reloading the page. So all the information is there. I don't think information about opting out of all crash reporting is actually appropriate for this article.

Also the plugin-in crash UI is changing to make reloading + opting-in and out easier - https://bugzilla.mozilla.org/show_bug.cgi?id=665196

Thanks, Michael. Removing the section altogether is much better. I approved your revision.

I would like the "-1" to be inside a pref or something so its not like the rest of the text, but i dont know what the correct way to write it.

Like this ?...

setting {pref dom.ipc.plugins.timeoutSecs} to {pref -1}

{pref dom.ipc.plugins.timeoutSecs to -1}

but why you want to do that ? maybe it is better to bold the -1, -1(like the dom.ipc.plugins.timeoutSecs) :-)

The name and the value should be seperated. {pref dom.ipc.plugins.timeoutSecs to -1} dont make sense.

Making it bold it better then nothing but it seems {pref} might be made for this. But i'm not sure.

I made a revision to change it to this and left it pending review :

setting the {pref '''dom.ipc.plugins.timeoutSecs'''} preference to {pref '''-1'''}.

OK, but i think it is not needful ! Now do we have to find every preference {pref} in every article and change them to {pref.........}  :-) probably we discuss it more than worth !

a good change is to write where to change the dom.ipc.plugins.timeoutSecs to -1 (in about:config) because the article does not mentioned that (only in the next "the Mozilla Developer Network documentation" link referred) ! :-):-):-)

cheers

I'm guessing the Developing for Flash with Flex? section was purposely vague about setting the dom.ipc.plugins.timeoutSecs preference to -1 because it's aimed at more advanced users (developers) and it links to a Mozilla Developer Network article. I think that it's OK to leave out how to use about:config because the What if I don't want to terminate hung plugins? section of the MDN article says,

See about:config on MozillaZine for information on changing preferences like this one.

... and advanced users follow links!

sohailmazumdar

In any website it gets tedious to navigate with or without a mouse. To make things easier if shortcuts could be introduced the user can be benefited. Eg. Switching to different panes or search bars

AliceWyman said

... and advanced users follow links!

+1

AliceWyman said

I made a revision to change it to this and left it pending review : setting the {pref '''dom.ipc.plugins.timeoutSecs'''} preference to {pref '''-1'''}.

I'll approve this myself, as a minor revision.

A few thoughts:

  1. I’ve seen at least one revision change where pref markup was used for preferences and their values allright, but the bold markup within them was removed. Other and more recently changed articles tend to use them more often, but not always. Can we have a general guideline for it in order to use consistent pref markup? I’d prefer to use the pref markup only - it’s clear enough and probably intended to substitute bold markup.
  2. This pref change edit is another example of an edit treated as minor, while in fact it is not, IMO.
  3. Therefore locales have been behind more than a year following this edit.
  4. With item 1 in mind, slow approvals may be either a little useless or, based on new insights, may need new edits rather than approvals sometimes.

Edit: I added a blank line in r126232 in order to get a proper (one line) text-image spacing, also eliminating the issue of an image sticking to the right side of the previous text, which oddly only appears for non-en-US locales and is visible in this revision of the Dutch version.

Tonnes said

<snip> Edit: I added a blank line in r126232 in order to get a proper (one line) text-image spacing, also eliminating the issue of an image sticking to the right side of the previous text, which oddly only appears for non-en-US locales and is visible in this revision of the Dutch version.

Do you want your edit to add a blank line to be marked ready to localize?

The rest of your post probably belongs in a separate discussion, probably in the main Knowledge Base articles forum, since it's about policy affecting all KB articles.

I would say yes, since this is an issue all locales suffer from when editing/updating and so it can be avoided, so the sooner the better. IIRC, we never use image lines below a text line without indentation (;), and you know about that discussion.

I used regular pref markup in my locale’s version - feel free to add or ignore that change for en-US.

Tonnes said

I used regular pref markup in my locale’s version - feel free to add or ignore that change for en-US.

I used regular pref markup in my locale’s version too. I prefer to use the pref markup without the bold markup within.