667345 - Thunderbird Hangs at Master Password Dialog

Status: RESOLVED DUPLICATE of bug 659613

(Thunderbird :: Security, defect)

Description

[selwyn.james]

User-Agent:       Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20100101 Firefox/5.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11

This bug has similarities with bug 542498, but does not appear to be related to background processing.

Problem: Thunderbird Hangs at Master Password Dialog, if you don't login quickly (the length of this time limit is unknown). This appears to be a total application hang, as the only possible recovery I have found is to kill the process.

I have a lot of email managed by Thunderbird, plus I have Lightning 1.0b2 installed. OS is XP SP3.

Reproducible: Always

Steps to Reproduce:
1. Start Thunderbird.
2. Configure Master Password.
3. Restart Thunderbird.
4. Do not login immediately (wait a few minutes).
5. Thunderbird hangs.
6. Kill thunderbird.exe.
7. Repeat (100% repeatable).

Actual Results:  
App hangs with Hourglass.

Expected Results:  
App should sit and wait indefinitely for user to login.

Easy workaround: Restart Thunderbird and don't go off and get a coffee while you wait...

Comment 1

[Ludovic Hirlimann [:Usul]]

Ok I can't reproduce. Does it works better if you start Thunderbird in -safe-mode (see http://support.mozillamessaging.com/en-US/kb/Safe-Mode) ?

If not could you get us a stack trace as per https://developer.mozilla.org/en/how_to_get_a_stacktrace_with_windbg ?

Comment 2

[selwyn.james]

Attachment: Thunderbird stack trace, as requested.

Note: This is a Thunderbird stack trace (as per https://developer.mozilla.org/en/how_to_get_a_stacktrace_with_windbg), not a Firefox one (as implied by the name).

Also note:
a)  I have now upgraded to Thunderbird 6.0 (since this bug was first submitted) and this problem still exists.
b)  I did not get any errors in the debugger and had to use the Break command.

Comment 3

[selwyn.james]

Sorry, forgot to add: Safe mode had no effect.

Comment 5

[mike.sorice]

(In reply to [:Aureliano Buendía] from comment #4)
> 
> *** This bug has been marked as a duplicate of bug 659613 ***

You'll excuse my ignorance, but is this really a duplicate of 659613 and how can we be sure? 659613 is a crash, whereas this is a hang. Also, the stack trace of this hang doesn't contain the crash signature of 659613, which I suppose may follow a fortiori from the previous statement.

I'm experiencing essentially the same bug on OS X, c.f. bug 715805.