524315 - shutdown hang, high cpu, no open imap connections, no ldap connections but has live, blocked ldap threads

Status: RESOLVED FIXED

(MailNews Core :: LDAP Integration, defect)

Description

[Wayne Mery (:wsmwk)]

Attachment: windbg info for hang

+++ This bug was initially created as a clone of Bug #494014 +++

shutdown hang, high cpu, no open imap connections and no ldap per netstat
20091016 build on XP, so it has all recent shutdown hang patches I think.
but maybe a dupe

when I shut down there was a compose window open and I responded "don't save" to drafts dialog.

Comment 1

[Wayne Mery (:wsmwk)]

Attachment: windbg info for 3.0rc1 hang

same hang?

also XP, but newer build - 3.0rc1 20091112

Comment 2

[Wayne Mery (:wsmwk)]

Attachment: windbg vista

same profile as previous two hangs, only the profile has been moved to vista.
and Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.5) Gecko/20091209 Shredder/3.0.1pre

Comment 3

[Wayne Mery (:wsmwk)]

removed one of my accounts from checking for new mail at startup and logging in to it, for a day now i'm not hanging on shut down.

Comment 4

[Chris Kolar]

Resolved in Eudora 8b9 using TB 3.0.1 base.

Comment 5

[Wayne Mery (:wsmwk)]

changing bug version - I've been using v3.1 for about a month, currently Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.2pre) Gecko/20100316 Lanikai/3.1b2pre. My imap account is SSL/TLS, stored password, check every 2 minutes for messages, check on startup


> Resolved in Eudora 8b9 using TB 3.0.1 base.

Hi Chris. Your issue is then bug 494014 which was fixed in v3.0.1.

Comment 6

[Wayne Mery (:wsmwk)]

Attachment: TB windbg stacktrace wsm v3.1 20100405.txt

bienvenu, can you check this stacktrace?

this was most unexpected.  since comment 3 I've been shutting down great for a couple weeks now. Just before this last shutdown, I reinstated the account mentioned in comment 3, setting it to check for new mail on startup. I saved a draft and did file, restart (I have restart add-on installed)...shutdown hung

netstat (127.0.0.1 seems odd - is symantec fooling with me?)
  TCP    127.0.0.1:57570        FS001AA0A76435:57571   ESTABLISHED
 [thunderbird.exe]
  TCP    127.0.0.1:57571        FS001AA0A76435:57570   ESTABLISHED
 [thunderbird.exe]
  TCP    127.0.0.1:57572        FS001AA0A76435:57573   ESTABLISHED
 [thunderbird.exe]
  TCP    127.0.0.1:57573        FS001AA0A76435:57572   ESTABLISHED
 [thunderbird.exe]

Comment 7

[David :Bienvenu]

the ldap thread is still active. Perhaps a leaked ldap connection.

Comment 8

[Wayne Mery (:wsmwk)]

bienvenu, do stacks from first 3 comments also point to ldap?
attachment 408227 [details] 
attachment 412975 [details] 
attachment 417215 [details]

Comment 9

[David :Bienvenu]

(In reply to comment #8)
> bienvenu, do stacks from first 3 comments also point to ldap?
Yes, they all have live ldap threads that are blocked.

Comment 10

[Wayne Mery (:wsmwk)]

this may be optimistic, but I got positive preliminary results with today's nightly ftp://ftp.mozilla.org/pub/thunderbird/nightly/latest-comm-central/ which has ldap bug 343332 fixed. 

I did three shutdowns so far and no hang. (but one crash)
Will report back in a  few days on whether the problem is totally gone.

Comment 11

[Wayne Mery (:wsmwk)]

After two days, I'm reasonable confident this is fixed by bug 343332