Поиск в Поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Подробнее

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.