Closed Bug 305113 Opened 19 years ago Closed 19 years ago

apparent looping when loading message with many attachments from IMAP server

Categories

(Thunderbird :: Mail Window Front End, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: jim, Assigned: mscott)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6 Build Identifier: Thuderbird version 1.0.2 (20050317) I received an e-mail with 73 attached JPG files, each of which was a little under 100K. The mail is stored on a Kerio Mail Server with an IMAP interface. Thunderbird seemed to be processing this in an unending loop. I was able to verify that the mail itself and Kerio were OK by fetching it with an older version of Mozilla. Reproducible: Always Steps to Reproduce: 1. Receive a mail with more than 70 JPG attachments, each of about 100K in size 2. Verify that the mail is present on your IMAP server by looking in inbox 3. Click on the message to view it. Actual Results: Apparently endless looping. Not a crash, but network access continued and CPU activity was heavy. It was possible to stop this by attempting to load another message from the inbox. Expected Results: Just load the mail and provide normal access to it and to its attachments.
I can confirm that it does the same here with Thunderbird 1.0.7 (20051217) (Gentoo Linux kernel 2.6.14). What thunderbird is doing it's that when it wants to display an attachment (show attachments inline) it's downloading the full message. So for the 70 jpgs user the "endless" loop it's just that thunderbird is downloading the mail 70 times. In my case the IMAP server was UW IMAP4rev1 v12.264.
please try a 1.5 build - this was fixed on the trunk a long time ago.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → WONTFIX
sorry, meant wfm.
Status: RESOLVED → UNCONFIRMED
Resolution: WONTFIX → ---
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago19 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.