Cerca nel supporto

Attenzione alle mail truffa. Mozilla non chiederà mai di chiamare o mandare messaggi a un numero di telefono o di inviare dati personali. Segnalare qualsiasi attività sospetta utilizzando l'opzione “Segnala abuso”.

Ulteriori informazioni

Questa discussione è archiviata. Inserire una nuova richiesta se occorre aiuto.

Profile bug? "unresponsive plugin" Shockwave (/questions/970014)

  • 11 risposte
  • 27 hanno questo problema
  • 1 visualizzazione
  • Ultima risposta di mountaincrawlie

more options

I have the unresponsive plugin shockwave problem

I have the unresponsive plugin shockwave problem

Soluzione scelta

Just FYI I didn't use firefox for a few days, and was about to try these solutions but it seems to be working now - I assume someone somewhere has done an update that has fixed things, so fingers crossed. Thanks all for your input,

J

Leggere questa risposta nel contesto 👍 0

Tutte le risposte (11)

more options

It is possible that anti-virus software is corrupting downloaded files or is otherwise interfering with downloading files.

Try to disable the real-time (live) scanning of files in your anti-virus software temporarily to see if that makes downloading work.

See:

http://kb.mozillazine.org/Unable_to_save_or_download_files browser.download.manager.scanWhenDone 0

more options

Hi - thank you for your answer but the downloading is not really the problem, it is the crashing unresponsive shockwave plugin that I want to solve - thanks

more options

You can check for problems with current Flash plugin versions and try these:

  • disable a possible RealPlayer Browser Record Plugin extension for Firefox and update the RealPlayer if installed
  • disable protected mode in the Flash plugin (Flash 11.3+ on Windows Vista and later)
  • disable hardware acceleration in the Flash plugin
more options

Sorry, tried this and didn't solve the problem either. Thanks

more options
more options

All the plugins are up to date - it is still doing it and I don't really want to just suppress the problem by choosing not to be told about it - thanks though

more options

The Warning Unresponsive plugin - What it means and how to fix it article also says this:

...which links to a section of the Flash Plugin - Keep it up to date and troubleshoot problems article. One of the Flash troubleshooting suggestions there is to disable hardware acceleration in the Flash plugin:

  • Disable HW acceleration in Flash:
    1. Go to this Flash help page on adobe.com.
    2. Right-click on the Flash Player animation then click Settings in the context menu. The Adobe Flash Player Settings screen will open.
    3. Click on the icon at the bottom-left of the Adobe Flash Player Settings window to open the Display panel.

      The image "fpSettings1.PNG" does not exist.
    4. Remove the check mark from Enable hardware acceleration.
    5. Click Close to close the Adobe Flash Player Settings Window.
    6. Restart Firefox.

Did you try that? cor-el also suggested it. This Adobe page has details on that setting. For more on disabling Flash hardware acceleration, see

more options

Hi, yes, thank you for persisting, ... I did try disabling the hardware acceleration but it is still crashing ...

more options

If Firefox or the Adobe Flash plugin is crashing, do you have a crash Report ID?

  1. Enter about:crashes in the Firefox address bar and press Enter. A Submitted Crash Reports list will appear, similar to the one shown below.
  2. Copy the 5 most recent Report ID's that start with bp- and paste them into your response here.

SubmittedCrashReports-Win7

Thank you for your help!

more options

P.S. Your "more system details" list shows that all of your Firefox extensions are deactivated EXCEPT for Firebug, which is known to cause crashes. Try setting ALL extensions, incuding Firebug, it to "Never Activate" in the Firefox Add-ons Extensions list and then restart Firefox.

Does that solve the problem?

more options

Soluzione scelta

Just FYI I didn't use firefox for a few days, and was about to try these solutions but it seems to be working now - I assume someone somewhere has done an update that has fixed things, so fingers crossed. Thanks all for your input,

J