Closed Bug 1092591 Opened 10 years ago Closed 9 years ago

IMAPS Access stuck after Network Outage

Categories

(MailNews Core :: Networking: IMAP, defect)

All
macOS
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: u522202, Unassigned)

References

Details

(Keywords: hang, stackwanted)

User Agent: Mozilla/5.0 (iPad; CPU OS 8_1 like Mac OS X) AppleWebKit/600.1.4 (KHTML, like Gecko) Version/8.0 Mobile/12B410 Safari/600.1.4

Steps to reproduce:

I try to access an already authenticeted and opened IMAPS account after a network outage.


Actual results:

The connection stucks and there is no response from Thunderbird. Thunderbird must be restarted.


Expected results:

Thunderbird should be able to access the IMAPS account after a network outage. Thunderbird must not be restarted.
OS: Mac OS X → All
Hardware: ARM → All
No duplicate of bug 1092593, see my comments there.

Furthermore Thunderbird with this bug is reacting to mouse clicks and can be closed normally.
Severity: normal → major
Component: Untriaged → Mail Window Front End
Does taking Thunderbord offline, then online make imap functional again?
Component: Mail Window Front End → Networking: IMAP
Flags: needinfo?(info)
Product: Thunderbird → MailNews Core
See Also: → 1092593
I will drop a message when the error occured again, possibly this would take some days.
Severity: major → critical
Keywords: hang
Up to now the error did not occur again because there was no network outage so far.  So we have to wait.
(In reply to info from comment #5)
> Up to now the error did not occur again because there was no network outage
> so far.  So we have to wait.

No problem. When it does hang again, before killing the process please get a stacktrace using 
https://developer.mozilla.org/en-US/docs/How_to_get_a_stacktrace_for_a_bug_report#OS_X 
attach the file to the bug report and reopen the bug please.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Flags: needinfo?(info)
Keywords: stackwanted
OS: All → Mac OS X
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.