With recent builds (last week and 11/20/01, osx), I can't check my IMAP mail. it just sits and spins with the staus "Opening folder..." Clicking stop crashes (another bug filed on that). Can't check email at all. 6.2 works just fine.

cc'ing darin, since yesterday i told him this had gone away. sorry, darin. It came back this morning with the same bits.

Darin is this related to the url parsing changes? We have several XP smoketest blockers today that are caused by a check in to nsURLParsers.cpp. This could be a symptom of that as well.

Hey Mike, when you say it came back today with the same bits do you mean it came back with today's release bits? Or using an older build where it was working, it is now showing this problem?

i used a build from last week, it didn't work. i used a build from yesterday and it worked yesterday but the same bits (yesterday's) don't work for me today.

pink: build from last week? before friday? if so, then it would seem that this wouldn't have anything to do with URL parsing, since the URL parsing changes landed thursday evening.

I'm running a release build on OSX from yesterday and I don't see this. So I don't think it's effecting everyone. I'd like to take this off the smoketest list but still leave it as a blocker for me to investigate today. Is that okay with you Mike?

taking off the smoktest list but leaving as a P1 blocker. I will try to get in a state where I can reproduce this today. For starters, can you create an imap log and send it to me? Steps to do that are here: http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#imap

as long as somone is looking at it. i want to test some nspr patches for smfr on my dual-cpu box, but this is blocking me from doing that. Perhaps it's a dual-cpu thing again in another form if others aren't seeing it and only I am.

in addition to the imap log, which build from last week did you first notice this problem?

this works fine for me with today's packaged bits, just not at all in my debug tree. how could they be different?

oh, dear, i have no idea. i think it was like last thursday or something (again, my own debug build). i haven't been working much on the trunk of late, so i just figured i'd pulled at a bad time. i'll get that log now.

the imap log file taken from my 11/19/01 debug build

according to the log we did all the work we are supposed to. When it just sits and spins, is the thread pane blank?

yes, the threadpane is blank and the progress meter is indeterminant and spinning. clicking stop crashes.

I actually cannot reproduce this problem on my MacOS 10.1 on commercial 11-20-04-trunk build...

i also see lots of these assertions: +++ nsGenericModule nsMsgSMIMEModule: unable to create factory for {9e4b07ee-e980-11d2-a506-0060b0fc04b7} And also this js exception: failed to get view & sort values. ex = [Exception... "Component returned failure code: 0x80004003 (NS_ERROR_INVALID_POINTER) [nsIMsgFolder.getMsgDatabase]" nsresult: "0x80004003 (NS_ERROR_INVALID_POINTER)" location: "JS frame :: chrome://messenger/content/commandglue.js :: FolderPaneSelectionChange :: line 683" data: no]

Mike, try moving away your Inbox.msf file (don't delete it, since if it's causing the problem, we'd need to debug why). Do you see any assertions from Mork when you run a debug build?

when i moved the file away, nothing happened when i launched mail (it didn't try to load any folder since i no longer had an inbox). clicking on another imap folder started to open and stalled. i put the file back and i can use mail just fine with 6.2.

Hello -- is it possible this issue is related to '104481'. The intermittant delays for mailbox access has been magnified with Nov20_096 -- specific to "save copy.." and "save draft.." when using IMAP over SSL. -GA

Mike would have told us if he was using SSL, right? :-) I'll try SSL on windows.

IMAP SSL on windows works fine. Save draft worked fine (no performance difference) with a build from a tree pulled 11/20.

ah-ha! so it works the _first_ time (when component reg is done) and then never again. the first time I don't get any of the factory errors or asserstions about [nsIMsgFolder.getMsgDatabase]. Every time after, i do. wasn't this a different blocker? at what point was that backed out? The build i'm currently working with was pulled at about 3:30pm PST on 11/20.

yes, just confirmed it takes two runs of mozilla to see this happen. tossing the component reg makes the bug go away, but then the next time you run moz, mail is broken again.

Hey, mscott, could this smime stuff be involved? nsGenericModule nsMsgSMIMEModule? Or is that a red herring? Are all the factory assertions involving SMIME? Does the registry get screwed up if we have a problem registering a factory?

I think the smime thing is a red herring. But it is strange that Mike would see that assertion many times in the 3-pane. In theory we would never load that module unti you brought up the mailnews account manager. I do think the reason we never stop spinning is because of the JS error: [nsIMsgFolder.getMsgDatabase]" nsresult: "0x80004003 (NS_ERROR_INVALID_POINTER)" location: "JS frame :: chrome://messenger/content/commandglue.js :: FolderPaneSelectionChange I bet that exception causes us to break out of our JS code before we turn the busy signal off......

is this bug really Mac only? (i can't test it on windoze, my installation is shot)

marina reports seeing this as well in a different bug with a build from a day or two ago. I'm not alone ;)

Question (probably for Mike or David), I'm seeing this when I go offline. I am assuming it's the same bug and not a new offline bug. I've seen this in the current builds. Very easy to reproduce: -login in to imap mail -click offline icon -don't download at the prompt -go back online -click on a folder result: imap spins. No mesgs appear. Just get the hourglass for mouse and spinning barber pole. The only way to get out is to exit the application and restart it. If it's a new bug, please let me know. I only see this on Mac builds.

fwiw, this still happens with my 12/11/01 debug build. the 12/11/01 opt build works fine. ideas?

I am seeing this same issue, build 2002030808. However it does only seem to happen on my INBOX, subfolders seem to work alright.

Sean, can you attach a protocol log, and edit out any sensitive info? http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#imap thx.

reassigning to bienvenu.

Mike, can you still recreate this, and if so, could you attach a protocol log? thx.

i can't reproduce this w/commercial trunk 2002031107 on 10.1.3

ADT Needs info: who is seeing this and is there any more info. we can get for a reproducable test case? Marina can you still see this?

this magically went away for me. i haven't seen it in a while. again, it worries me when networking problems magically go away, but....

Sean, do you still see this?

same for me... i haven't seen it for a while, somehow went away.

Maybe my PR_Poll fix from Friday fixed this?

Simon, maybe, though it sounds like it went away for pink and marina before Friday...if it has gone away. I'm going to mark wfm, and we can re-open it if it happens again.

Verified WFM.

I have this problem consistently when using IMAP over SSL. I use Netscape 7.0 ( Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0.1 Gecko/20020826) on Mac OS X 10.2.1. I have had it too on earlier Mozilla versions and on Netscape 7. I'd love to give you a log file but the procedure in http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#imap does not work for me. I drag the text file onto the icon and mozilla opens, displaying just the text file. I cannot find a log file either. Maybe I'm misunderstanding the instructions? Matthias (berth at decodon.com)

please download a new trunk build. The ssl issue on the mac was fixed a couple weeks ago, I believe.