Closed
Bug 292778
Opened 20 years ago
Closed 19 years ago
Moving emails to mail folders with a . (dot) in them is extremely slow
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: gboissiere, Assigned: mscott)
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322) Build Identifier: Build 20050317 I had a large folder (300 MB) called BR.com as a subfolder of my Inbox. When moving emails from my Inbox to this subfolder, it sometimes (10% of the time) took several minutes to perform the operation, as if Thunderbird was re- indexing the whole folder from scratch. Same thing would happen with a rule to automatically move incoming emails to that folder. Thunderbird would freeze for 5 minutes, and then come back up after the message was moved. Renaming the folder to BRcom as a workaround fixed this issue and I have not seen this behavior for 2 weeks since I made the change, so it must be a problem with the . in the middle of the folder name. Reproducible: Sometimes Steps to Reproduce: 1. Create a subfolder called BR.com as a subfolder of Inbox and put several thousands message in it 2. Create a rule to move some incoming messages to this BR.com subfolder 3. Leaves Thunderbird open for a couple hours 4. Click on "Get Mail" with an email that will trigger the rule Actual Results: Thunderbird froze for three minutes to move a short message to the BR.com subfolder, as if it was reconstructing the whole folder from scratch. After three minutes, it was back up and working as expected. The message was properly moved to the folder. Expected Results: Moving the message should be instantaneous. Renaming the folder to BRcom as a workaround fixed this issue and I have not seen this behavior for 2 weeks since I made the change, so it must be a problem with the . in the middle of the folder name.
Comment 1•19 years ago
|
||
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 2•19 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•