Thunderbird 52.1.1 Ubuntu 16.04 Hanging Regularly
Not sure why, as I don't recall installing any updates prior to experiencing this, but Thunderbird is hanging quite regularly in the last two days. It hangs quite a bit upon launching (5-10s) and then operates normally for a few more seconds and hangs on and off every 5-10s thereafter. It never crashes, and thus no crash reports to debug from, nor does anything popup showing that anything is wrong, it just goes gray and is unusable for a few seconds, and returns to normal, but it does this so regularly that I cannot even write a short email.
I've tried restarting in thunderbird's safe mode, and nothing changes.
I'm not quite sure what to look for, but tried searching this log:
export NSPR_LOG_MODULES=IMAP:4
export NSPR_LOG_FILE=~/tbird.log.txt
for things like "error" and "denied", and "failed", but didn't see anything looping or anything that looked particularly strange. Here is an excerpt that showed the only matches for any of the above keywords (though this same pattern seems to occur for most of my mail accounts, including those outside of gmail):
1787819776[7f4b6d646980]: 6c9a4800:imap.gmail.com:NA:CreateNewLineFromSocket: 1 OK Thats all she wrote! s67mb233695657qka
1787819776[7f4b6d646980]: try to log in
1787819776[7f4b6d646980]: IMAP auth: server caps 0xc080c1625, pref 0x800000000, failed 0x0, avail caps 0x800000000
1787819776[7f4b6d646980]: (GSSAPI = 0x1000000, CRAM = 0x20000, NTLM = 0x100000, MSN = 0x200000, PLAIN = 0x1000,
LOGIN = 0x2, old-style IMAP login = 0x4, auth external IMAP login = 0x20000000, OAUTH2 = 0x800000000)
1787819776[7f4b6d646980]: trying auth method 0x800000000
1787819776[7f4b6d646980]: IMAP: trying auth method 0x800000000
1787819776[7f4b6d646980]: XOAUTH2 auth
1655678720[7f4b6d647280]: ReadNextLine [stream=67ec8300 nb=173 needmore=0]
1655678720[7f4b6d647280]: 67e1c800:imap.gmail.com:NA:CreateNewLineFromSocket: * CAPABILITY IMAP4rev1 UNSELECT IDLE NAMESPACE QUOTA ID XLIST CHILDREN X-GM-EXT-1 XYZZY SASL-IR AUTH=XOAUTH2 AUTH=PLAIN AUTH=PLAIN-CLIENTTOKEN AUTH=OAUTHBEARER AUTH=XOAUTH
1647286016[7f4b6d6473a0]: ReadNextLine [stream=67ec8880 nb=173 needmore=0]
1647286016[7f4b6d6473a0]: 68222000:imap.gmail.com:NA:CreateNewLineFromSocket: * CAPABILITY IMAP4rev1 UNSELECT IDLE NAMESPACE QUOTA ID XLIST CHILDREN X-GM-EXT-1 XYZZY SASL-IR AUTH=XOAUTH2 AUTH=PLAIN AUTH=PLAIN-CLIENTTOKEN AUTH=OAUTHBEARER AUTH=XOAUTH
1647286016[7f4b6d6473a0]: ReadNextLine [stream=67ec8880 nb=45 needmore=0]
1655678720[7f4b6d647280]: ReadNextLine [stream=67ec8300 nb=43 needmore=0]
1647286016[7f4b6d6473a0]: 68222000:imap.gmail.com:NA:CreateNewLineFromSocket: 1 OK Thats all she wrote! v16mb231876655qge
1655678720[7f4b6d647280]: 67e1c800:imap.gmail.com:NA:CreateNewLineFromSocket: 1 OK Thats all she wrote! a39mb6042816qvh
1647286016[7f4b6d6473a0]: try to log in
1655678720[7f4b6d647280]: try to log in
1647286016[7f4b6d6473a0]: IMAP auth: server caps 0xc080c1625, pref 0x800000000, failed 0x0, avail caps 0x800000000
1655678720[7f4b6d647280]: IMAP auth: server caps 0xc080c1625, pref 0x800000000, failed 0x0, avail caps 0x800000000
1647286016[7f4b6d6473a0]: (GSSAPI = 0x1000000, CRAM = 0x20000, NTLM = 0x100000, MSN = 0x200000, PLAIN = 0x1000,
LOGIN = 0x2, old-style IMAP login = 0x4, auth external IMAP login = 0x20000000, OAUTH2 = 0x800000000)
1655678720[7f4b6d647280]: (GSSAPI = 0x1000000, CRAM = 0x20000, NTLM = 0x100000, MSN = 0x200000, PLAIN = 0x1000,
LOGIN = 0x2, old-style IMAP login = 0x4, auth external IMAP login = 0x20000000, OAUTH2 = 0x800000000)
1647286016[7f4b6d6473a0]: trying auth method 0x800000000
1655678720[7f4b6d647280]: trying auth method 0x800000000
1655678720[7f4b6d647280]: IMAP: trying auth method 0x800000000
1655678720[7f4b6d647280]: XOAUTH2 auth
1647286016[7f4b6d6473a0]: IMAP: trying auth method 0x800000000
1647286016[7f4b6d6473a0]: XOAUTH2 auth
I've also checked the System Monitor and it doesn't look like Thunderbird is using an obscene amount of RAM or CPU, nor do I notice anything looking like a bottleneck in the Network History, or otherwise.
Any tips on what to check to keep debugging this? I'm not really sure where to look from here.
Other useful info: Thunderbird 52.1.1 Ubuntu 16.04
Ausgewählte Lösung
Thanks for your reply, but I managed to get it working a few days ago.
I'm not exactly sure which step of my troubleshooting did it, though it seems to have been a hard disk issue. I'm not sure what in the Thunderbird runtime was writing to the disk at a 5-10 sec interval, but I assume it could have been a number of things.
After finding a few repetitive peaks in the I/O readings using some terminal monitor that I now forget the name, I ran a few checks on my HDD, and found a number of bad sectors. I can't say definitively if this is what solved it, but I followed some forum advise from my Windows 10 partition, and ran a chkdsk script through cmd (with now forgotten parameters) and it gave me a lot of messages about fixing random things.
I also hacked away at the mbox files in the Linux partition quite a bit prior to seeing the hard disk errors, so splitting up large ones, or deleting the msf files might have had something to do with it as well.
Sorry I didn't keep better track of this. I'll try to help anyone who replies to this with similar problems though if I can.
Diese Antwort im Kontext lesen 👍 0Alle Antworten (3)
Sorry you have had trouble. Please update to 52.2.1 to fix a gmail problem, which might fix your issue. It might redownload messages once after the update, but then it should no longer redownload.
If you still have trouble check tools, Activity Manager for events.
Please post your results
Ausgewählte Lösung
Thanks for your reply, but I managed to get it working a few days ago.
I'm not exactly sure which step of my troubleshooting did it, though it seems to have been a hard disk issue. I'm not sure what in the Thunderbird runtime was writing to the disk at a 5-10 sec interval, but I assume it could have been a number of things.
After finding a few repetitive peaks in the I/O readings using some terminal monitor that I now forget the name, I ran a few checks on my HDD, and found a number of bad sectors. I can't say definitively if this is what solved it, but I followed some forum advise from my Windows 10 partition, and ran a chkdsk script through cmd (with now forgotten parameters) and it gave me a lot of messages about fixing random things.
I also hacked away at the mbox files in the Linux partition quite a bit prior to seeing the hard disk errors, so splitting up large ones, or deleting the msf files might have had something to do with it as well.
Sorry I didn't keep better track of this. I'll try to help anyone who replies to this with similar problems though if I can.
topher217 said
Sorry I didn't keep better track of this. I'll try to help anyone who replies to this with similar problems though if I can.
Glad to hear you fixed it. Even better that you posted your findings that might help someone else. We have lots of users who need help, and can always use more volunteers