We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Mozilla サポートの検索

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.

詳しく学ぶ

このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。

V 31.0 and new script busy problem

  • 4 件の返信
  • 19 人がこの問題に困っています
  • 7 回表示
  • 最後の返信者: DonGateley

more options

Since 31.0 site loading takes three or four time as long as 30.0 did. FF is now pretty close to useless. Possibly related is that since 31.0 I am getting very frequent warning messages about unresponsive scripts. The content of these messages varies.

Since 31.0 site loading takes three or four time as long as 30.0 did. FF is now pretty close to useless. Possibly related is that since 31.0 I am getting very frequent warning messages about unresponsive scripts. The content of these messages varies.

選ばれた解決策

Let's deal with those unresponsive script messages.

Type about:support in the URL bar and hit Enter.

Look at the list of Extensions and try to match up an extension with the code in that error message - the two lines containing Jetpack. Then try disabling those extensions.

この回答をすべて読む 👍 2

すべての返信 (4)

more options

Since I can't add them to the original post I include here a screen shot of the most recent warning window I encountered. I'd copy and paste the contents instead if your warning boxes allowed text copying. Hint, hint.

Please fix FF and release the fixed version soon so it becomes useful again. Don't tell me to use safe mode because that is not the environment in which the failure occurs.

more options

選ばれた解決策

Let's deal with those unresponsive script messages.

Type about:support in the URL bar and hit Enter.

Look at the list of Extensions and try to match up an extension with the code in that error message - the two lines containing Jetpack. Then try disabling those extensions.

more options

I found a match up. The jid0-dII4p... matched the "Short Link" plugin. I disabled that and will wait a bit before I decide it was successful and the problem is solved but frankly I'd be quite surprised if I see that one again.

I believe I saw problems with other scripts prior to that one and will see if they yield to this diagnostic.

I really thank you for cluing me to about:support and this way of diagnosing unresponsive script problems.

more options

It's been ten hours of browsing without a recurrence of the script hang so I consider this problem happily solved! Regained performance loss I saw with 31.0 as well. Thanks again.