1608733 - close/cancel original message while sending reply causes TB to hang

Status: RESOLVED DUPLICATE of bug 1610406

(Thunderbird :: Untriaged, defect)

Description

[webmaster2]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:72.0) Gecko/20100101 Firefox/72.0

Steps to reproduce:

I open a received message, click Reply, write a reply message, click Send, then close the original message before the reply message is finished sending. TB hangs and I need to force quit TB (Mac). When I close the original message, I am doing that by clicking the red X icon in the upper left of the message (Mac).

I have seen this happen many times over the past months. Most of those occurrences have been on my home ISP which is Viasat (satellite).

In order for the error to occur, the sending of the reply message needs to be sufficiently delayed – if it completes very quickly, there's no time to close the original message. What is governing how fast the sending takes I don't know, but I suppose it is related to how fast the remote mail server is responding, but could also be related to the network, or some other factor. If there's a delay of a few seconds, this allows the bug to appear because that's sufficient time for me to close the original message.

I just saw this bug happen while using a fast cable broadband connection, but I'm not able to reproduce it because the sending of the reply is completing immediately. The bug may be possible to reproduce on my home ISP which is a Viasat satellite connection, so I will give that a try and report the results.

I am using TB version 68.4.1 on Mac OS X version 10.11.6.

Actual results:

The reply message may or may not be sent successfully, and TB is unresponsive and needs to be closed via Mac's Force Quit. Force Quit indicates TB "not responding". I have waited a long time (a minute?) in some cases and TB never resumes.

Expected results:

Original message gets closed, reply message gets sent normally, and TB does not hang.

Comment 1

[Jorg K (CEST = GMT+2)]

Surely a duplicate of bug 1381485.

Comment 2

[webmaster2]

I recommend this bug report (bug 1608733) should not be lumped together with bug 1381485, which is 3 years old and appears to have become a catch-all for cases where TB hangs on the Mac, even though these cases may not have the same underlying root cause. Btw, bug 1381485 mentions two other bug reports where TB hangs on the Mac.

I think my bug report will give a chance at zeroing in on this particular case where TB hangs during sending a message. My hunch is that the hang only occurs when the duration of the sending process is sufficient, which then allows the replied-to message to be closed, which causes the hang.

If a method can be determined to reliably cause the sending process to delay sufficiently, then the bug can be easily reproduced. This could then in turn result in the cause being found.

Comment 3

[Wayne Mery (:wsmwk)]

Indeed extremely high probability to be bug 1381485. There are users there who can reproduce it almost at will, we just need to determine the source of the bug.

Comment 4

[Wayne Mery (:wsmwk)]

See my Bug 1610406 comment 23. If they are the same issue then you should be getting a crash report, as I do when I use your steps to reproduce. You can find your crash reports at Help > Troubleshooting

Comment 6

[webmaster2]

I will try to reproduce it. When TB hangs, how do I generate a crash report?

Comment 7

[Wayne Mery (:wsmwk)]

(In reply to webmaster2 from comment #6)

I will try to reproduce it. When TB hangs, how do I generate a crash report?

If you have crashed in the past you should have a list of them in help > troubleshooting - scroll down to "Crash Reports for the Last 3 Days" and "All crash reports". If there is no list, then the crash reporter isn't working and you need to use windbg. The process is described at https://wiki.developer.mozilla.org/en-US/docs/Mozilla/How_to_get_a_stacktrace_with_WinDbg in terms for Firefox. Just substitute "Thunderbird" wherever you see "Firefox".