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.