254735 - Looses network connection and must be restarted to connect again

Status: RESOLVED DUPLICATE of bug 173924

(Thunderbird :: General, defect)

Description

[Markus Baertschi]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Opera 7.50  [en]
Build Identifier: Thunderbird version 0.7.2 (20040707)

When Thunderbird is running for a long time hours/days it eventually looses the 
network connection. I see three different effects when this happens:
1) Clicking on 'Get Mail' gives no reaction at all
2) If I'm writing a mail and want to send it I get a server timeout
3) Connecting to a news server times out
Just stopping and starting Thunderbird cures the problem. I have observed this 
behaviour since version 0.5.

Reproducible: Always
Steps to Reproduce:
1. Start Thunderbird
2. Work on other stuff and keep it running for hours
3. Work with Thunderbird and find it no longer connects to its servers

Actual Results:  
The network connection was lost

Expected Results:  
Just keep connecting

What can I do to help pinpint the problem (switch on debug logs, etc) ?

Comment 1

[Markus Baertschi]

Attachment: Sending mail, after clicking on 'Send'

Comment 2

[Markus Baertschi]

Attachment: Sending mail, after closing the window

Comment 3

[Markus Baertschi]

Attachment: Sending mail, after clicking on 'Quit' (previous dialog box)

Comment 4

[Markus Baertschi]

Attachment: Opening nes server, notice status line

Comment 5

[Markus Baertschi]

I've left the machine running since the bug submission yesterday and TB is now 
in its broken state.
- When I click on 'Get mail' nothing happens (it is supposed to connect to my 
mail server and fetch new mail)
- When I send a mail the send mail window just hangs looking up the domain name 
of the mail server
- When I want to read news TB attempts to connect (see status line) but just 
sits there forever
I attach screen shots of my actions (send mail, including the popups when I 
cancel the message, open the news server)

Comment 6

[jwq]

I believe this may be a duplicate of Bug 227617.

Comment 7

[Markus Baertschi]

I just hat a look at 227617 and it looks indeed very similar. 

Comment 8

[Max Alekseyev]

*** This bug has been marked as a duplicate of 173924 ***