Avatar for Username

搜尋 Mozilla 技術支援網站

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

了解更多

此討論串已被封存。 如果您有需要幫助，請新增一個新問題

Firefox hangs with unresponsive script error since new release of 41.0.2

  • 1 回覆
  • 3 有這個問題
  • 1 次檢視
  • 最近回覆由 creeem

gguenther
gguenther
more options

Since updating to the latest version 41.0.2 our users are experiencing a large amount of unresponsive script errors on most sites. The error causes Firefox to hang and often requires it to be restarted. We have tried uninstalling it completely and reinstalling it, tried creating a new Firefox profile as well as a new computer profile. We have the latest updates of Java, Flash, etc. Other browsers (IE, Chrome, etc.) are not having an issue with the same pages. We have also tried the suggestion on the Mozilla support page "Warning Unresponsive script - What it means and how to fix it" but the issue persist.

Since updating to the latest version 41.0.2 our users are experiencing a large amount of unresponsive script errors on most sites. The error causes Firefox to hang and often requires it to be restarted. We have tried uninstalling it completely and reinstalling it, tried creating a new Firefox profile as well as a new computer profile. We have the latest updates of Java, Flash, etc. Other browsers (IE, Chrome, etc.) are not having an issue with the same pages. We have also tried the suggestion on the Mozilla support page "Warning Unresponsive script - What it means and how to fix it" but the issue persist.

所有回覆 (1)

creeem
creeem
more options

I get this problem with Twitter. I have noticed that when I keep twitter on and then the updates go above 3k or 5k If I it auto updates or try to do refresh my TL it will hang. This is because FF is already burdened My FF normally takes up 2gb of Ram (which i see from the task manager). Also if i have more than 10 tabs running it slowly becomes slower and slower. There are some Script intensive websites that can slow down firefox. I still feel its a FF problem cause i have not faced the same problem on Chrome.