702152 - shutdown hang blocked waiting for I/O

Status: RESOLVED DUPLICATE of bug 634526

(Thunderbird :: General, defect)

Description

[Wayne Mery (:wsmwk)]

Attachment: windbg stacktrace

daily build 20111108.
vista laptop

netstat...

  TCP    127.0.0.1:52175        Wayne-D531:52176       ESTABLISHED     6564
 [thunderbird.exe]
  TCP    127.0.0.1:52176        Wayne-D531:52175       ESTABLISHED     6564
 [thunderbird.exe]
  TCP    127.0.0.1:52177        Wayne-D531:52178       ESTABLISHED     6564
 [thunderbird.exe]
  TCP    127.0.0.1:52178        Wayne-D531:52177       ESTABLISHED     6564
 [thunderbird.exe]

Comment 1

[David :Bienvenu]

is this reproducible/new? I haven't landed anything recently that should affect this.

Comment 2

[Wayne Mery (:wsmwk)]

(In reply to David :Bienvenu from comment #1)
> is this reproducible/new? I haven't landed anything recently that should
> affect this.

I did several restarts in a short period of time, and don't recall what done on that particular restart.  At one point I may have done steps similar to bug 639393. 

I don't know that it's new, in part because I don't use thunderbird much on this laptop, but also because I rarely hang ... indeed the last new bug I filed was Bug 639393 - shutdown hang after closing drafts with 3pane already closed.  That was a long time ago.

Comment 3

[Wayne Mery (:wsmwk)]

bienvenu, 
is there anything definitively useful in this stack?
If not then I'm happy to close this - not reproducing in recent weeks

Comment 4

[David :Bienvenu]

(In reply to Wayne Mery (:wsmwk) from comment #3)
> bienvenu, 
> is there anything definitively useful in this stack?
> If not then I'm happy to close this - not reproducing in recent weeks

We're blocked waiting for I/O - it's not "not useful", but it doesn't show us doing anything wrong either, if that makes sense. It seems that we got an idle response, perhaps right before shutdown. We don't handle idle responses once shutdown has started, because we check m_threadShouldDie before calling HandleIdleResponse, and the very first thing we do as part of the shutdown process is tell all the imap connections that the thread should die.

Comment 5

[Wayne Mery (:wsmwk)]

(In reply to David :Bienvenu from comment #4)
> We're blocked waiting for I/O - it's not "not useful", but it doesn't show
> us doing anything wrong either, if that makes sense. It seems that we got an
> idle response, perhaps right before shutdown. We don't handle idle responses
> once shutdown has started

similar to bug 634526 comment 9 ?

Comment 6

[David :Bienvenu]

(In reply to Wayne Mery (:wsmwk) from comment #5)
> (In reply to David :Bienvenu from comment #4)
> > We're blocked waiting for I/O - it's not "not useful", but it doesn't show
> > us doing anything wrong either, if that makes sense. It seems that we got an
> > idle response, perhaps right before shutdown. We don't handle idle responses
> > once shutdown has started
> 
> similar to bug 634526 comment 9 ?

Could very well be.

Comment 7

[Wayne Mery (:wsmwk)]

OK. we'll see after bug 634526 is fixed :)

Comment 8

[Wayne Mery (:wsmwk)]

Let's assume they are the same. I can't currently reproduce anyway