為了改善您的使用體驗,本網站正在進行維護,部分功能暫時無法使用。若本站的文件無法解決您的問題,想要向社群發問的話,請到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 發問,我們的社群成員將很快會回覆您的疑問。

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

System regularly hanging with Adobe Flash/Shockwave Flash?

  • 2 回覆
  • 23 有這個問題
  • 1 次檢視
  • 最近回覆由 delcrab

more options

When my Shockwave Flash plugin is enabled, it causes FireFox 4.0 to regularly hang when visiting websites. All I will see is a white background and an hourglass, then I will see "...Mozilla Firefox (not responding)".

If I disable it the plugin, then I can't watch video on most websites. How do I get flash working with Firefox 4.0?

By the way -- it didn't work with my old version of flash -- I just updated flash five minutes ago to the latest version and it still doesn't work.

When my Shockwave Flash plugin is enabled, it causes FireFox 4.0 to regularly hang when visiting websites. All I will see is a white background and an hourglass, then I will see "...Mozilla Firefox (not responding)". If I disable it the plugin, then I can't watch video on most websites. How do I get flash working with Firefox 4.0? By the way -- it didn't work with my old version of flash -- I just updated flash five minutes ago to the latest version and it still doesn't work.

所有回覆 (2)

more options

I have been experiencing the identical issues as described above on an HP dv7 Notebook with ATI Radeon H3200 Graphics card. This seems to have started after downloading a bunch of Microsoft Windows updates a couple of days ago. I now have to keep the Shockwave Flash plug-in (10.2.153) disabled or each new web page I try to view hangs for 45-60 seconds. As a work-around I have been using Chrome to view web content requiring Adobe Flash.

more options

It appears I was able to resolve this problem by following all of the steps here: https://support.mozilla.com/pa-IN/questions/808868#answer-166820

I downloaded the latest Shockwave Flash plug-in (10.2.159) specifying the version for Firefox. Maybe version 159 tweaked the plugin container and stopped the "not responding" issue. Fingers-crossed.