Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

Thunderbird seizes when starting with McAfee addon installed

  • 2 답장
  • 19 이 문제를 만남
  • 3 보기
  • 최종 답변자: Wayne Mery

more options

When starting, Thunderbird locks up/seizes. The GUI cannot be selected or modified. After a while the following error message appears: "A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete.

Script: chrome://messenger/content/toolbarIconColor.js:48"

It does not seem to matter whether one selects CONTINUE or STOP, after a while Thunderbird starts to work normally. Although, it seizes completely and I must use the Task Manager to stop it.

I am using Thunderbird 45.2.0 running under Windows 10.

When starting, Thunderbird locks up/seizes. The GUI cannot be selected or modified. After a while the following error message appears: "A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete. Script: chrome://messenger/content/toolbarIconColor.js:48" It does not seem to matter whether one selects CONTINUE or STOP, after a while Thunderbird starts to work normally. Although, it seizes completely and I must use the Task Manager to stop it. I am using Thunderbird 45.2.0 running under Windows 10.

글쓴이 Wayne Mery 수정일시

선택된 해결법

Problem appears to have been solved. Started Thunderbird in the safe mode and disabled the extension "McAfee Anti-Spam Thunderbird Extension". This appears to have done the trick as Thunderbird starts faultlessly.

문맥에 따라 이 답변을 읽어주세요 👍 3

모든 댓글 (2)

more options

선택된 해결법

Problem appears to have been solved. Started Thunderbird in the safe mode and disabled the extension "McAfee Anti-Spam Thunderbird Extension". This appears to have done the trick as Thunderbird starts faultlessly.

more options

LamtonWorm - presumably both Thunderbird and McAfee has updated in the past two months.

So do you still experience this problem if you re-enable the addon?