327312 - Timeout when attempting to retrieve large IMAP inbox

Status: RESOLVED INCOMPLETE

(Thunderbird :: General, defect)

Description

[Ben]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
Build Identifier: Thunderbird 1.5

When trying to open a large IMAP inbox using Thunderbird 1.5 in headers only mode, I get a timeout message almost immediately.  I was hoping to upgrade to 1.5 from 0.7.3 (20040803) which works fine and does not have the same issue.

Reproducible: Always

Steps to Reproduce:
1. Get a large inbox (35919 messages, 1.3GB would be ideal ;-)
2. Get Thunderbird 1.5
3. Configure for IMAP, headers only, and the message will appear, every time

Actual Results:  
Timeout message appears

Expected Results:  
Let me read my email.

Comment 1

[Ben]

A bit more version info :

Thunderbird 1.5 (20051201)
Mac OS X 10.4.5 BUILD 8H14

Comment 2

[David :Bienvenu]

ouch, I was hoping this was the windows multi-processor bug. Perhaps its related. The default timeout is 60 seconds, but you're getting the message way before that? Tools | options | advanced - lets you specify the timeout in seconds.

Comment 3

[Ben]

Hi, 

I did pick up that other bug, but I noticed that the user there was "occasionally" able to see emails, I can't see any, hence my self-justification of opening a new bug.

Anyway, down to business ....


It's "Thunderbird ==> Preferences ==> Advanced" on the mac, as you say, set to 60 seconds.

I'd say about 30 seconds max (depends if I go to double click on a cached header or not, it happens a little sooner - probably 20-25 seconds - on cached headers).

This is on a dual 500 G4 .... not one of those fancy intel thingies by the way ;-).   With 768 meg of ram... running with about 200MB free at the moment.

Comment 4

[David :Bienvenu]

but it is a dual processor machine? Interesting; it might really be a similar problem in the OS. Anyway, you can try increasing that timeout, perhaps to a number like 65,530, and see if your problem goes away.

Comment 5

[Ben]

I was just trying to do that (changing timeout number to something silly) , but only just realised I had to quit and re-open Thunderbird for the setting to take effect (Feature Request on its way after I've done a bit of searching on bugzilla).

Set on 6000 seconds, it works ;-)

But we've hit and passed 2 minutes .... probably verging on 2 minutes 15.   And that happens every time, even after a quit and reload with cached headers.

After 0.7.3 has loaded the first time, the second time round after quit and re-open takes 60 seconds or less.

Comment 6

[Kaj Kandler]

Not sure if this is the very same problem. I see Thunderbird 1.5.0.7 timeouts also, once the IMAP folder goes over 12K messages. I can usually read the headers but then I can't delete or move any messages. It times out after 30-60 seconds.

My machine is not a dual processor but an AMD Athlon single processor. My IMAP server is courier IMAP 3.0.8-3 on SuSE 9.2. I found that disabling the IMAP-IDLE in Advanced options, right the ship for me. May be that works for you too and narrows down the bug.

Comment 7

[Wayne Mery (:wsmwk)]

is this gone for everyone when using version 2?

Comment 8

[Joshua Cranmer [:jcranmer]]

RESO INCO due to lack of response to prior comment.

If you believe this change was made in error, please respond with your reasons why, preferably by providing a response to the question in previous comment.