搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

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?