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

Shockwave Flash crashing

  • 73 பதிலளிப்புகள்
  • 656 இந்த பிரச்னைகள் உள்ளது
  • 61 views
  • Last reply by Mikey

Shockwave Flash 12.0.0.77 keeps crashing. It was only installed on 14 March 2014 and I am told it is up to date. I am running Firefox 28.0 on Windows 7 home premium.

The message I get is Warning: Unresponsive Plugin Shockwave Flash maybe busy, or it may have stopped responding, <snip>

I used to get this with an older version of Shockwave Flash and an older verison of Firefox, but in the last few days it has started to happen again (since I updated Firefox to the latest version).

Shockwave Flash 12.0.0.77 keeps crashing. It was only installed on 14 March 2014 and I am told it is up to date. I am running Firefox 28.0 on Windows 7 home premium. The message I get is Warning: Unresponsive Plugin Shockwave Flash maybe busy, or it may have stopped responding, <snip> I used to get this with an older version of Shockwave Flash and an older verison of Firefox, but in the last few days it has started to happen again (since I updated Firefox to the latest version).

தீர்வு தேர்ந்தெடுக்கப்பட்டது

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

  • disable protected mode in the Flash plugin (Flash 11.3+ on Windows Vista and later)
  • disable hardware acceleration in the Flash plugin

See also:

Read this answer in context 👍 9

All Replies (20)

Those crash reports haven't been submitted (Invalid crash ID)

If you have submitted crash reports then please post the IDs of one or more recent crash reports that have a "bp-" prefix:

  • bp-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

You can find the IDs of the submitted crash reports on the about:crashes page.

  • You can open the about:crashes page via the location bar, like you open a website, or open the crash reports page via "Help > Troubleshooting Information".

See:

Let's try that again https://crash-stats.mozilla.com/report/index/bp-a93af6a7-bf09-409d-956d-64b8c2140515

This is the most recent "bp" crash report.

Thanks

my crash reports. 7880d7ed-a2c5-4c8b-a196-30fe38fc5890 5/24/2014 10:37 AM b27d2fad-ecee-4d29-9fcc-e98f0f2cad06 5/21/2014 5:09 PM b0196ef9-8a8c-42fe-9384-7ebfbfd214f6 5/15/2014 10:15 PM aa21d49e-cf11-4324-8317-172a37bb32d1 5/15/2014 10:09 PM f7f2e856-928f-45e1-a500-69b0e03ff12e 5/8/2014 8:26 AM

After years of the same problem with no solution coming from Firefox, it would seem obvious that the answer is to dump Firefox for a more reliable browsing experience.

N30rebel மூலமாக திருத்தப்பட்டது

I totally agree with you N30rebel as it seems they have no intention of solving this problem.

Am looking for a good alternative to Firefox.

what i can't figure out is shockwave will crash over & over.....the plugin says it's up to date, i'll keep reloading the page, and then suddenly it's working just fine...... wtf?????

It is frustrating, especially to read of someone's successful attempt to fix the situation and yet not have the same solution work for me. Taking the problem to a tech is a waste because they're not conversant with this issue. I much prefer MF to IE, but am fed up.

i'm computer inept.....beyond the *power on* and X-ing out of windows/tabs it's all chinese to me.....i know what IE is, but what's MF???? oh nevermind.... mozilla firefox.....silly me!! oh well.....at least i know how to type!!! ;)

i do agree though....i much prefer firefox to explorer....IE seems *chunky* to me..... and i like chrome, but i just really like the way ff performs.... (except when shockwave crashes, right!!)

Perhaps MF will be inspired to expedite a solution in order to keep some of us from going to the dark side.

hahahaha.......NEVER!!!!!!

It is not Mozilla you should be mad at though, it is Adobe for making a bad product and not fixing issues that have been going on for months. They are the biggest name in video player software yet have had so many issues keeping it up to date and error free. I'm not a programmer but this specific issue is something I would be working day and night to fix because it effects so many people. I personally have updated everything I could and even tried to revert to an older player yet still get the same error. I read that it was a driver issues or a graphics card issue as well but I have a AMD 7700 which is only about a year old, not top of the line but is still good and only a couple months old with up to date drivers. Turn your attention to Adobe not Mozilla for the issue.

Thank you for the insight into the source of the problem. So, do you see a timeline for a solution?

I HAVE complained to Adobe and they Do have "solutions" - usually to uninstall Adobe shockwave/flash and reinstall, and if that doesn't work to uninstall and reinstall an older version. There is even an uninstaller to download. Unfortunately, even that doesn't work sometimes (and it seems like we go through this problem every few months after an FF update).

Problematically, while Shockwave crashes in Firefox, it rarely crashes in IE or Chrome. I know because I have to switch to them when FF is crashing just to get to the support at either Adobe OR Firefox. Therefore, for some reason, Firefox and Adobe do NOT play well together. Given this has happened over years - at least since about 4.0 (and yes FF seems headed towards 30), it SEEMS that it is something integral within FF that keeps tripping up Adobe, and then the FF team does a tweak or something changes and then everything works fine again for a while.

OR... maybe it is plugins that we use that throw things into the mix and cause the crashes (sometimes true) as there have been a couple of times over the years that I have been able to open in safe mode and not crash.

I do NOT want to switch. I love Firefox (most of the time) and certainly it stands heads and shoulders above IE and Chrome (in my opinion and the way that I use a browser). Further, there are plugins that I use that have no equivalents in the other browsers. I do not want to lose them by moving to another browser, OR by running FF in safe mode.

This is a recurring problem. I wish it would get resolved. It seems clear that IF it is going to get fixed, it will need to be on the Firefox team as I imagine that Adobe responds to money (even while providing a "free" plugin) and clearly both Microsoft and Google have money to burn and our much loved Mozilla Firefox does not. Using the usually successful "follow the money" trail to the culprit would seem to support this conclusion.

It does NOT make it any less of a problem, and unfortunately I imagine that it does cost Firefox some users - perhaps even loyal ones.

I detect a sense of resigned exasperation in your reply. I think we all share it. In this age of wonders, how can the solution to a problem like this remain so elusive?

well said.....my thoughts exactly.....(applause)

How did you remove them from your plug in list? I only get the options of activate, ask to activate or never activate for the ms plug in. Which I have set to never.

You can start here: https://support.mozilla.org/en-US/kb/disable-or-remove-add-ons

Follow the link "How to uninstall plugins." Under "Manually Uninstalling," after you rename the indicated file name by placing an X in front of it, check the tools>add ons>plugins and you will see that there are now a number of options including "remove." now

thank you.....yup, done all that.....what's really weird is it will start doing it out of the blue, and then *just stop*......hmmmmmmmm

this was an answer i got from someone else....mine seems to be weird, it will crash over and over, and then suddenly just....stop....is that strange or what??

You can start here: https://support.mozilla.org/en-US/kb/disable-or-remove-add-ons

Follow the link "How to uninstall plugins." Under "Manually Uninstalling," after you rename the indicated file name by placing an X in front of it, check the tools>add ons>plugins and you will see that there are now a number of options including "remove." now

  1. 1
  2. 2
  3. 3
  4. 4