If a plugin causes issues right after an update then the plugin is not compatable. That is regardless of what Adobe claims about their plugins...

nathansuchy -- Not to be rude, but please read my post carefully: "My FF had crashed occasionally before FF 20.0 but mostly due to Adobe Flash plug-in container. "

So the plug-in did not crash my FF after the update. It had happened for a long time. Adobe didn't claim that, plug-in check is a Mozilla product.

Not to be offtopic but have you turned your computer off recently (the crash report looks like corupted ram) please turn your computer off for 60 seconds then turn it back on and tell me your results.

I turn off and restart my laptop every morning after a virus/spywares scan check overnight.

cor-el -- I haven't tried safe mode yet since it will disable all of my extension. And moreover, it might take some time to test if my extensions are the problems. I'll try to find time to test in Safe Mode. When I do, I'll post my update here later. Probably won't be for a few days.

Thank you.

guys, i have the same problem as silkphoenix. Shockwave Plugin just constantly crashing, or hangs and I can browse again once I disable the plugin from the message box. Is there a real fix to this?? Have anyone try to downgrade shockwave plugin? Perhaps only newer version is having issue

Hi papalin, if you have Windows Vista / 7 / 8, could you try the steps listed in this other thread: https://support.mozilla.org/en-US/que.../955929#answer-425312. If you have a different operating system/version, or if those steps do not help, please start a new question with your system particulars and add-ons listed. You can do that here:

https://support.mozilla.org/en-US/questions/new/desktop/fix-problems

Hi silkphoenix, I looked at the four crash reports that start with bp and nothing leaps out at me -- because for me the information is simply at too technical a level, and the links into the bug system do not give any clear answers.

You do indeed have a lot of extensions (about 35?). I can appreciate the pain of browsing without essential extensions that you use many times a day. However, if you could disable the ones that you could part with for 24 hours, I think that might be a reasonable intermediate test.

orange Firefox button (or Tools menu) > Add-ons > Extensions category

Thanks Jscher2000, I will give it a try! Hopefully this would fix the issue on FF 20.0 with adobe flash crash issue.

jscher2000 -- Thank you for your reply. Yes, I do have a lot of extension. That's one of the reasons I love Firefox which enable me to use those extensions. I like Chrome too (mainly because it has never crashed on me). But its lacking of extensions is a big disappointment. I'll try to find time to test them.

papalin -- You might try the add-on "Flashblock". I installed that a few days ago and Flash hasn't crashed on me yet. Though you do need to do one more step before you can play any flash movies (but it's a small price to pay to avoid the crash and hanging), or you can put those sites in the whitelist.

OK, My FF 20.0 crashed two times yesterday and then three times today. Here are the crash report from today, in case some of you have time to read them and see if they shed any lights on the problems:

bp-1bcd5405-4ed8-467c-875f-1422a2130410 bp-96b855f8-77f3-40bb-9649-65a422130410 bp-8dfb3b74-311f-4a22-82ea-449452130410

I did create a new profile and it didn't help.

I still couldn't find time to check all the extensions since I have quite a few. But I doubt if they are the problems since I haven't added any new ones, they are all the same as in FF 19. Unless some of the extensions' updates and FF 20.0, somehow causing issues with each other.

I do have a question and it might have something to do with my frequent crash, I am not sure. I have recently (in the last few days) have Chrome opened at the same time with FF 20 because I need to use my Google Voice, somehow it doesn't work in my FF (hasn't been for a long time) but works in Chrome, and also a couple other websites which do not work properly with FF. The crash almost happen about the same time I updated to FF 20 from 19. It could be a co-incidence. But I just want to throw it out as something to consider.

Thank you.

I'll stop using Chrome tomorrow for a day, using just FF to see if there's any crash. Maybe I can eliminate that possibility. I'll post a update here later.

Hi silkphoenix, thank you for the updates.

New Profile. When you created the new profile, did you run without the extensions for a while, or did you migrate them? If the crash occurred in a new profile with no extensions, that would diminish the probability that they were involved with the issues in your regular profile.

Fx Upgrade. Firefox 20 could well be a factor: there are so many changes in each release that it's impossible to rule out one of them.

Concurrent use of Chrome. Firefox and Chrome really should run in isolation from one another, although perhaps they might share a few resources, such as Flash local storage objects if you are visiting the same sites in both browsers. (Considering third party content in pages, this might not be as rare as I thought.)

Crash Reports. One of the crash reports contains data (two were corrupt) and it seemed very similar to previous crashes. When I poke around, the problem seems to be related to Shape::search() but that doesn't mean a lot to me.

Partial Safe Mode. You could partially simulate Firefox's Safe Mode by disabling one other feature (you already disabled hardware accelerated graphics) and that is the JavaScript Just-in-Time (JIT) compiler. To do that,

(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 filter box, type or paste jit and pause while the list is filtered

(3) Double-click each of the following preferences to toggle them to false:

• javascript.options.methodjit.chrome
• javascript.options.methodjit.content

I don't know whether that takes effect immediately or upon a restart.

Honestly at this point, try a fresh profile, as this is a Javascript crash, and coule be caused by any number of dozens of things.

Hi Silkphoenix,
you are usually answering questions not asking them.

I note you do say that you have tried another profile, but we are not sure if it is a clean one. You may also have seemed reluctant to try Firefox's safemode. Lets try to clear up some potential misunderstandings.

Disable plugins when using safemode or a newprofile
Safe mode amongst other things temporarily disables extensions and hardware acceleration. It does not now have permanent effects unless you use the separate reset feature. You will obviously note it does not disable plugins. (Otherwise you would not be able to test Flash Player in safemode.)

Windows Safe mode
It is probably worth testing in Windows safemode (with networking) that will take some other potential culprits out of other frame.

• http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/boot_failsafe.mspx?mfr=true

FlashProtected mode
You are only using XP, otherwise I may have suggested turning that off.

(Note to self - I keep meaning to try the Chrome plugin as the Firefox Flash-player )

Hi John99,

Yes, you are right, I usually answering questions and rarely asking. But sometimes, when you don't even know how to solve a problem yourself, the best thing is to ask for help.

I just want to post a brief update.

I updated to FF 20.0.1 on April 11, and since then, my FF hasn't crashed for two days. I don't know if it's a co-incidence, or some of my plug-ins' updates fixed the issue. But whatever it is, so far no crash.

I'll post another update in a few days to see if there's any more crashes.

Thank you to everyone for all of your kind comments/suggestions/advices.