This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

Gettiong chrome://messenger/content/mailWindow.js:179 error but after while works fine. Two accounts and appears worse with one account

  • 1 reply
  • 6 have this problem
  • 2 views
  • Last reply by Matt

MikeLouissville
MikeLouissville
more options

when starting up Thunderbird, it's very slow. Running version 24.6.0 on Windows 8.1. Computer is a ASUS laptop. Have two email accounts. One account works fine but the other one is very slow at beginning. Clicking or deleting emails I get no response until after about 30 seconds. At times I also receive the following error message "chrome://messenger/content/mailWindow.js:179'. Clicking on stop script doesn't help. After about 4 minutes, get normal response times. This is after I have clicked or deleted emails aout five times.

when starting up Thunderbird, it's very slow. Running version 24.6.0 on Windows 8.1. Computer is a ASUS laptop. Have two email accounts. One account works fine but the other one is very slow at beginning. Clicking or deleting emails I get no response until after about 30 seconds. At times I also receive the following error message "chrome://messenger/content/mailWindow.js:179'. Clicking on stop script doesn't help. After about 4 minutes, get normal response times. This is after I have clicked or deleted emails aout five times.

All Replies (1)

Matt
Matt
  • Moderator
  • Top 10 Contributor
more options

About 5 minutes is how long it takes anti virus programs to scan the Thunderbird profile folder. Perhaps you need to exclude the profile folders from "on access" scanning and leave it to full scans to look at that part of the disk.