Overview Description: First time use of an IMAP account, that has been freshly created, results in a huge, memory-chewing, infinite loop (until app ultimately dies). Steps to Reproduce: 1) delete users50 directory, and mozregistry.dat, mozver.dat (i.e., as if this is a very first time installation). Install mozilla (netscape 6) 2) start browser 3) click on mailnews icon (wizard comes up) 4) select 'other ISP' and hit next 5) choose IMAP and I used judge.mcom.com for both incoming and outgoing (SMTP) server 6) don't give it a password in the wizard (will be prompted later) 7) finish the wizard with the default fields entered 8) mailnews is now up with two folder in collapsed state: jrgm@netscape.com and 'local folders' (in my case) 9) open twisty on jrgm@netscape.com, and click on INBOX 10) enter password when prompted and hit enter Actual Results: If you have wintop on win9x (or task manager on winNT [If this happens on winnt]), you should now see mozilla running with 95+% of CPU. On windows 95, eventually the disk begins to grind as swapping occurs. Wintop tells me that the process image is way above 150MB. Eventually, mozilla crashes. Expected Results: Like, you know ... Reproducibility: 100% on 2000051908 win 95 Build Date & Platform Bug Found: 2000051908 win 95 Additional Builds and Platforms Tested On: none; setting up for four crashes on win95 was enough for me Additional Information: I have submitted talkback ID's but the stack traces are useless; they only have one-line (and that line is likely just the routine that was running when available memory hit zero -- i.e., it's the victim). Here is what I had in the console window. The javascript error is unrelated I think (it's just dismissing off the tooltip when clicking the INBOX). Note: all of these messages precede the actual infinite loop (so they may not tell you much). ---------------------------------------------------------------------- WSM.PageData[login][][nodeName] : label; WSM.PageData[login][][elType] : null; WSM.PageData[login][password][excluded] : false; WSM.PageData[login][password][value] : ; WSM.PageData[login][password][id] : password; WSM.PageData[login][password][nodeName] : input; WSM.PageData[login][password][elType] : password; WSM.PageData[accname][prettyName][excluded] : false; WSM.PageData[accname][prettyName][value] : jrgm@netscape.com; WSM.PageData[accname][prettyName][id] : prettyName; WSM.PageData[accname][prettyName][nodeName] : input; WSM.PageData[accname][prettyName][elType] : text; Setting identity for jrgm@netscape.com am.createIncomingServer(jrgm,judge.mcom.com,imap) am.createIdentity() am.createAccount() Looking for Local Folders..... finding folders on server = Local Folders fccFolder = mailbox://nobody@Local Folders/Sent draftFolder = mailbox://nobody@Local Folders/Drafts stationeryFolder = mailbox://nobody@Local Folders/Templates WEBSHELL- = 9 WEBSHELL- = 8 in showthreads JavaScript error: line 0: uncaught exception: [Exception... "Component returned failure code: 0x8 0004002 (NS_NOINTERFACE) [nsIRDFCompositeDataSource.GetTarget]" nsresult: "0x80 004002 (NS_NOINTERFACE)" location: "JS frame :: chrome://messenger/content/mail 3PaneWindowCommands.js :: FillInFolderTooltip :: line 729" data: no] imap://jrgm@judge.mcom.com/INBOX In ChangeFolderByURI WEBSHELL+ = 9 WEBSHELL+ = 10 WEBSHELL+ = 11 commonDialogOnLoad setting info.header to There are 2 buttons WEBSHELL- = 10 Move window by 0,20 screen x 0screen y 0 WEBSHELL- = 9 WEBSHELL- = 8 ---------------------------------------------------------------------- I will attach a zip of my profile as it stood at the time of the crash (it's primarily the default profile, with a minimal amount of information about my IMAP account) If you can't reproduce it, I'll show you on my system (and perhaps it's specific to win95 anyways).

Hmmm. On second thought I'm not going to attach my Users50 to a public web site :-], even if it is mostly vanilla stuff. But I will mail it to mscott/lchiang if they need it. I'll also note that when I restart mailnews, this newly created account works just fine; it's only when proceeding directly from creation to immediate use do I hit this loop (but that is a fairly common use case for new users of the application). Marking nsbeta2.

John, can you tell us the name of the server you were creating an account on at the time? Thanks...

I was using judge.mcom.com as the IMAP (and SMTP) server. I just tried this with the 2000052310 build on the same win95 machine, and I cannot reproduce this now -- which is good news and bad news, I suppose :-\ You can close this out, since it now works for me, or ask me to check this again in the next few days.

Okay, I'll close it out for now and we can re-open if you see it again. Thanks John.

Verified on 06-21-09-M17 commercial build. Brand new IMAP acct on virgin installation no Infinite Loop anymore.