If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Failed login when low memory available



9 years ago
8 years ago


(Reporter: Justin Bell, Unassigned)


Firefox Tracking Flags

(Not tracked)




9 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0
Build Identifier: version (20071031)

When an application that isn't Thunderbird, Thunderbird fails login to IMAP servers, including GMAIL and OTHER IMAP servers.

When the process taking up large amount of resources, Firefox, TiVo server, etc. Thunderbird often then succeeds in connection to IMAP server and retrieves headers.

Reproducible: Sometimes

Steps to Reproduce:
1. Open app that is a resource hog, let it hog memory
2. Thunderbird fails login
3. Kill app
4. Thunderbird works correctly
Actual Results:  
Expected results

Expected Results:  
It should have not reported failed login if resources were the issue
Better than crashing and also better then silently do nothing or do you expect an out-of-memory message ?

Comment 2

9 years ago
No need to be so adversarial.

What do I expect? Something that actually is relevant to the problem occurring maybe, Login to server failed doesn't exactly communicate what the problem is.

Comment 3

9 years ago
other than a code audit (which i'm unlikely to do for all of mail anytime soon...), you're going to need a stack trace showing this.

assuming the login failure can be seen in the form of a dialog, then two things will be useful:
1. a protocol log (google for how to get this)
2. a stack trace <http://developer.mozilla.org/en/docs/How_to_get_a_stacktrace_with_WinDbg>

you will need to run thunderbird w/ protocol logging active, and you should attach w/ windbg *before* you run out of memory :). once you've hit the dialog, use windbg to break into thunderbird. Note that you shouldn't load symbols in windbg eagerly as described in the url. instead only do them after you kill your memory hog.

the basic stacks we'd want are:
~* kp

but you may need more interesting things like a js stack. you'll probably also want to save your memory image (.hh .dump) because you'll probably want to use thunderbird a bit while you're waiting for us to ask more questions.

I typically recommend: .dump /maipwd /u /ba /c "comment" file
however you may not want to include some portion of that (specifically you probably want to skip archiving symbols as we can get them later).
justin, can you supply the information mentioned in comment 3?
=> incomplete due to no response

if you still see problem, please test beta before reopening bug with more information
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.