378758 - Multiple times same attachment downloading leading to very slow message loading

Status: RESOLVED WORKSFORME

(Thunderbird :: General, defect)

Description

[Artem Kuchin]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; InfoPath.1; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 1.1.4322)
Build Identifier: 2.0.0.0 (20070326)

I had this problem in TB1 and now i still have in in TB2. 
The server and the client are both on local 100Mbit LAN. 
Server is: coourrier-imap on FreeBSD 
Client: TB2 on XP Pro SP2 

Conneting only over IMAP. 

Problem: When i click on a message with attachment (for example 1MB) i have to wait for about 30-40 seconds 
while message is loaded. In MS OE it loads instantly. 

Now, i turned on debugging in imapd and here is what i see:

WRITE: * 18 FETCH (BODY[2.MIME] {204} 
Content-Type: image/jpeg; 
name="=?koi8-r?B?b3V0ZG9vciDPwszP1svBLmpwZw==?=" 
Content-Transfer-Encoding: base64 
Content-Disposition: attachment; 
filename="=?koi8-r?B?b3V0ZG9vciDPwszP1svBLmpwZw==?=" 

BODY[2] {820278} 

Now after that WEIRD stuff happens. This fetch for BODY[2.MIME] is repeated MANY times. 
After that BODY[4.MIME] fetch is fetched about 10 times. 

logs and message are attached.


Reproducible: Always

Steps to Reproduce:
1. send yourself a message with 1MB image attached
2. try to receive it
3. monitor traffic and how much traffic and time it takes to load this message
Actual Results:  
Takes 30-40 seconds.

Expected Results:  
must take only a moment on 100MBit connection to imap server

Comment 1

[Artem Kuchin]

Sorry, could not attache files - they are TOO BIG (the form should mention it BEFORE i submit a bug). You can find all files at the following link:
http://www.artem.ru/tbbug

Comment 2

[Artem Kuchin]

Tested on 5 other PCs in same configuration (same client and same imap server software on lan). Got the same result.

Comment 3

[Artem Kuchin]

Hello! Anybody!!! Why is this problem ignored??? I am not the only one sufferring from it. I asked some friends also with the mail system layout and they all have the same problem! We all think about going back to MS OE because this is just impossible!!!

Comment 4

[Magnus Melin [:mkmelin] (away, back Aug 4)]

Does the view attachments inline setting change the behavior? Also, can you attach an imap protocol log? <http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#imap>

Comment 5

[Artem Kuchin]

No, i've read about 'view attchments inline' in many places. This is not it. Tried to turn it off and nothing changed. I wonder when someone from the development team will actually look at the logs i gave url to. It is all their, clearly.

Comment 6

[Magnus Melin [:mkmelin] (away, back Aug 4)]

Ah, you put the logs at http://www.artem.ru/tbbug. 

Comment 7

[Artem Kuchin]

So? Any progress on this bug?

Comment 8

[David :Bienvenu]

I looked at your log - all that's happening is that we look at the body structure, decide that all the parts are images so we should fetch the whole message because we're going to display all the parts inline, and then we fetch the whole message. It might be slow because we're fetching the message in large chunks - you could try turning chunking off - tools | options | advanced, config editor, toggle mail.server.default.fetch_by_chunks to false, and restart - does that speed it up?

I don't know why turning view |attachments inline off wouldn't speed things up. I'll try that with your sample message.

Comment 9

[David :Bienvenu]

I tried your sample message - everything worked as expected. We fetch the message once, and then use the memory cache to display the images (assuming you haven't turned off the memory cache). And if display attachments inline is off, we don't even fetch your images. So this bug is WFM as near as I can tell.

Comment 10

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

(In reply to comment #9)
> I tried your sample message - everything worked as expected. We fetch the
> message once, and then use the memory cache to display the images (assuming you
> haven't turned off the memory cache). And if display attachments inline is off,
> we don't even fetch your images. So this bug is WFM as near as I can tell.

WFM per comment #9.