1358332 - Thunderbird 52 intermittenly stuck "Connecting... " on MacOS X

Status: RESOLVED WORKSFORME

(Thunderbird :: Untriaged, defect)

Description

[Steve Chessin]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:52.0) Gecko/20100101 Firefox/52.0
Build ID: 20170323105023

Steps to reproduce:

I got a pop-up on my Windoze machine that Thunderbird 52 was available, so I downloaded and installed it. I didn't get a similar pop-up on my MacBookPro, which I found curious, so a few days later I went to https://www.mozilla.org/en-US/thunderbird/all/ (why can't I find this page from www.mozilla.org?) and downloaded 52.0.1 (https://download.mozilla.org/?product=thunderbird-52.0.1-SSL&os=osx&lang=en-US to be exact; I guess 52.0.1 had been released by then), installed it, and tried it. I found it unstable; it would connect to my work's IMAP server and let me open one message but if I clicked on a different one it would go into Connecting... and stay there an inordinate amount of time. If I toggled it from online to offline and back again it would sometimes then download the message I wanted, but not always.


Actual results:

See above.


Expected results:

It should have worked. I went back to using 45.8.0 (the last stable release for MacOS?).  Is this why I haven't gotten a pop-up about 52.0 or 52.0.1 on my MacBookPro, you haven't pushed it yet? (I'm running MacOS 10.9.5.)

Comment 1

[Wayne Mery (:wsmwk)]

Is the work imap an exchange server?
Does problem occur when started in safe mode https://support.mozilla.org/en-US/kb/safe-mode-thunderbird ?

Comment 2

[Wayne Mery (:wsmwk)]

FWIW in the past year there havent been any bugs that mention "connecting".
https://bugzilla.mozilla.org/buglist.cgi?list_id=13547290&o1=nowordssubstr&j2=OR&chfieldfrom=1y&o4=substring&v4=connecting.&f1=short_desc&o3=anywordssubstr&v3=connecting.&classification=Client%20Software&classification=Components&f4=longdesc&chfieldto=Now&query_format=advanced&f3=short_desc&f2=OP&product=MailNews%20Core&product=Thunderbird

Comment 3

[Steve Chessin]

(In reply to Wayne Mery (:wsmwk, NI for questions) from comment #1)
> Is the work imap an exchange server?

What is an exchange server? How would I be able to tell?

> Does problem occur when started in safe mode
> https://support.mozilla.org/en-US/kb/safe-mode-thunderbird ?

I'll give that a try and let you know.

Comment 4

[Jorg K (CEST = GMT+2)]

There are two protocols TB supports to receive e-mail: IMAP and POP3. Microsoft have invented another protocol, called "exchange" to talk between their Exchange servers and their Outlook clients. There is an add-on, ExQuilla, to add the exchange protocol to TB. However, MS Exchange servers can also talk IMAP if this is enabled.

So Ways wants to know what the IMAP server is. Dovecot or MS Exchange (with IMAP) or something else, see https://en.wikipedia.org/wiki/List_of_mail_server_software

Comment 5

[Steve Chessin]

I have no idea if the work imap server is an exchange server. However, I started TB 52 when I got to work today, and after a few hours it went unstable talking to gmail.com as well as to my work imap server. So I restarted it in safe mode, and after about 10 minutes it went unstable again (this time stuck in "Loading Message..."; telling it to Stop, toggling it offline and then online again, telling it to Get Messages, selecting an already-read message and then back to the one it got stuck on got it unstuck). 

Oh, and it just crashed. (How do I find the crash report? I know how to do that with FF.) I had crash reporting enabled, so maybe it got sent to you?

I've restarted it in Safe Mode, but if it crashes or goes unstable again I'm going to go back to TB 45.8.0.

Comment 6

[Wayne Mery (:wsmwk)]

> How do I find the crash report?
Under help > troubleshooting

Comment 7

[Steve Chessin]

Hmmm. I found this crash report:
https://crash-stats.mozilla.com/report/index/1d892dc2-aaf6-4227-9e5a-0e3c30170501
but it's from May 1st and my comment is from April 24th. The only other crash reports are from January 30th, 2016 and August 25th, 2015.

Oh, wait, those are *submitted* crash reports. If I click on All Crash Reports it shows me the unsubmitted ones. And sure enough, there's one from April 24th. Clicking on the link appears to do nothing. But if I right-click it I can get it to take me to https://crash-stats.mozilla.com/about/throttling/ which tells me:
You're seeing this page because the crash report you selected was held back from submission. For statistical purposes, we don't need every crash report and sometimes we decline the submission of a crash report as a form of throttling. If you'd like to see your crash report, type about:crashes into your location bar and your report will be automatically submitted to our server where we'll give it priority processing.

Of course, Thunderbird doesn't *have* a location bar. And putting about:crashes in FF's location bar only shows me the FF crashes.

So how do I submit an unsubmitted crash report?

Comment 8

[Wayne Mery (:wsmwk)]

Clicking on the unsubmitted crash submits it

Comment 9

[Steve Chessin]

(In reply to Wayne Mery (:wsmwk, NI for questions) from comment #8)
> Clicking on the unsubmitted crash submits it

I did that but it still shows up on the unsubmitted list, even if I close the Troubleshooting Information and Crash Reports tabs and redo Help -> Troubleshooting Information.

Comment 10

[Steve Chessin]

So how do I submit the crash report?

Comment 11

[Wayne Mery (:wsmwk)]

Perhaps the submission is blocked by your employer?

Comment 12

[Wayne Mery (:wsmwk)]

You most recent crash is bp-13222ce7-50d3-4240-9665-0bd730170614

Is life better if you disable Oracle Beehive?
It's been known to cause problems.

Comment 13

[Steve Chessin]

(In reply to Wayne Mery (:wsmwk, NI for questions) from comment #11)
> Perhaps the submission is blocked by your employer?

No, I tried it from home, and it doesn't send from there, either. I click on an unsubmitted crash report, and a blue spinning partial circle appears briefly, and then it goes away and nothing seems to have happened.

Anyway, I've long since rebooted and upgraded to 52.1.0 and 52.1.1 and now 52.2.0 and I think the problem went away when I went to 52.1.0.

Comment 14

[Wayne Mery (:wsmwk)]

> Anyway, I've long since rebooted and upgraded to 52.1.0 and 52.1.1 and now 52.2.0 and I think the problem went away when I went to 52.1.0.

With beehive enabled?

Comment 15

[Steve Chessin]

(In reply to Wayne Mery (:wsmwk, NI for questions) from comment #14)
> > Anyway, I've long since rebooted and upgraded to 52.1.0 and 52.1.1 and now 52.2.0 and I think the problem went away when I went to 52.1.0.
> 
> With beehive enabled?

Yes. I never disabled the Beehive extension.