Thunderbird on Mac locks-up inconsistently immediately after sending a message
Categories
(Thunderbird :: Untriaged, defect)
Tracking
(Not tracked)
People
(Reporter: chris, Unassigned)
Details
Attachments
(1 file)
|
2.27 MB,
text/plain
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:69.0) Gecko/20100101 Firefox/69.0
Steps to reproduce:
This has been happening to me multiple times per day for ... months or possibly years. I've been using tb since the beginning and I'm still sticking with it, but this is just crazy.
Full version info: 68.1.2; MacOS 10.14.6; extensions: Enigmail, Lightning.
Actual results:
Send an email message. As soon as the message window disappears, the color-wheel shows indefinitely over the main window. The only option is to kill tb using Force-Quit. I can get a full thread dump from Apple's crash reporter.
Expected results:
Umm.... no lock-up?
I'm a programmer with some experience, but not with C++/XUL/Rust. I'd love to instrument this thing and give someone exactly what they need to fix this.
|
||
Comment 1•5 years ago
|
||
Unfortunately Mac has some issues. The closest match for yours is bug 1381485 where some progress is being made, if slowly. For some users, https://support.mozilla.org/en-US/questions/1242885#answer-1179483 helps as a workaround
|
Reporter | |
Comment 2•5 years ago
|
||
Thanks for the quick reply. The message sends and the copy is put into the "sent mail" without any problems, so I don't think this is the same as bug #1381485.
This happens after the composition window has closed. I think it's a UI bug and has something to do with handling mouse events in the main window immediately after the message has been sent. Every time it locks-up, I am definitely moving the mouse, but then again.... I move the mouse a lot so that might not be a great data point.
It crashed again this morning, so I copied the thread dump to a file. I'm attaching it. Looks like a UI deadlock to me.
|
|
Reporter | |
Comment 3•5 years ago
|
||
|
|
Reporter | |
Comment 4•5 years ago
|
||
Agreed, this is a dupe of bug #1381485 given the thread dumps posted there. Not sure if CLOSING this issue is proper @mozilla.org, so feel free to take whatever BZ action you usually take when the matter won't be considered anymore. (BZ etiquette is different in different environments.)
Description
•