185700 - nsMsgImapLineDownloadCache::CacheLine() assertions when loading IMAP inbox.

Status: RESOLVED DUPLICATE of bug 171298

(MailNews Core :: Networking: IMAP, defect)

Description

[kinmoz]

Whenever I start up mail, and try to load my IMAP inbox with my Mozilla debug
build from 12/13/02, I hit tons of these assertion:


###!!! ASSERTION: Oops... line length greater than space available: '(PL_strlen(
line) + 1) <= SpaceAvailable()', file x:/mozilla/mailnews/imap/src/nsImapProtoco
l.cpp, line 259
Break: at file x:/mozilla/mailnews/imap/src/nsImapProtocol.cpp, line 259


At first I thought the summaries file for my inbox was corrupted, so I trashed
my ImapMail dir in my profile and restarted mail, but I'm still seeing tons of
assertions. This makes it almost impossible to load my inbox on Win32 since I
get a dialog for each assertion.

Here's the stack to the assertion:


NTDLL! 77f97704()
nsDebug::Assertion(const char * 0x06258cf0, const char * 0x06258cc4, const char
* 0x06258c94, int 259) line 280 + 13 bytes
nsMsgImapLineDownloadCache::CacheLine(nsMsgImapLineDownloadCache * const
0x01466948, const char * 0x059d1f18, unsigned int 130108) line 259 + 55 bytes
nsImapProtocol::HandleMessageDownLoadLine(const char * 0x05923e60, int 0) line 3197
nsImapServerResponseParser::msg_fetch_literal(int 0, int 0) line 2596
nsImapServerResponseParser::msg_fetch_content(int 0, int 0, const char *
0x06265318) line 1992 + 22 bytes
nsImapServerResponseParser::msg_fetch_headers(const char * 0x00000000) line 1966
nsImapServerResponseParser::msg_fetch() line 1110
nsImapServerResponseParser::numeric_mailbox_data() line 986
nsImapServerResponseParser::response_data() line 719
nsImapServerResponseParser::ParseIMAPServerResponse(const char * 0x05578e00, int
0) line 228
nsImapProtocol::ParseIMAPandCheckForNewMail(const char * 0x05578e00, int 0) line
1421
nsImapProtocol::FetchMessage(const char * 0x031da018, nsIMAPeFetchFields
kHeadersRFC822andUid, int 1, unsigned int 0, unsigned int 0, char * 0x00000000)
line 2925
nsImapProtocol::FolderMsgDumpLoop(unsigned int * 0x058ccfe8, unsigned int 7875,
nsIMAPeFetchFields kHeadersRFC822andUid) line 3567
nsImapProtocol::FolderMsgDump(unsigned int * 0x058ccfe8, unsigned int 7875,
nsIMAPeFetchFields kHeadersRFC822andUid) line 3470
nsImapProtocol::FolderHeaderDump(unsigned int * 0x058ccfe8, unsigned int 7875)
line 3449
nsImapProtocol::ProcessMailboxUpdate(int 1) line 3418
nsImapProtocol::ProcessSelectedStateURL() line 2134
nsImapProtocol::ProcessCurrentURL() line 1323
nsImapProtocol::ImapThreadMainLoop() line 1125 + 14 bytes
nsImapProtocol::Run(nsImapProtocol * const 0x054770a4) line 916
nsThread::Main(void * 0x05564db0) line 120 + 26 bytes
_PR_NativeRunThread(void * 0x05564ed0) line 433 + 13 bytes
_threadstartex(void * 0x055650b0) line 212 + 13 bytes

Comment 1

[kinmoz]

I should've mentioned this is with my Mozilla TRUNK build.

Comment 2

[(not reading, please use [e-mail] instead)]

if you try a new profile, do you still see it?

Comment 3

[kinmoz]

Yes, I see the assertions in a new profile ...

I created a brand new profile, launched mail, walked through the mail wizard to
set up a new IMAP mail account, and once it started downloading mail headers for
my inbox, the assertions started happening.

Comment 4

[Henrik Gemal]

this is happening if you have an IMAP mail message with a *long* To line.

not really sure it means. anyways this is a dupe

*** This bug has been marked as a duplicate of 171298 ***