搜尋 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?