User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; iOpus-Web-Automation; GTB5; .NET CLR 1.1.4322; .NET CLR 1.0.3705; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022; InfoPath.2; FDM; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729) Build Identifier: I selected an email inbox that had 30,000 unread messages. I marked the folder 'read'. Thunderbird memory proceeded to go through the roof. It got to 1.5GB (that is a 'G') of memory used. At the end of the operation it did go down (slowly) to a more reasonable level (took a long while to come down). Also, I often have to restart thunderbird because its memory usage exceeds 250MB. If its not a memory leak then for sure it not reclaiming its memory. Reproducible: Always
It actually took over 20 minutes to come back from the effort. -David
with that many messages a large amount of mem will be used. What version of TB are you using, did you create a new profile?
Component: Mail Window Front End → General
QA Contact: front-end → general
sounds familiar but I can't put my finger on the bug. When you say marked it read, did you do ctrl+shift+c? Or did you select all the messages and do "M" or mark as read?
I selected the folder and right clicked on it and selected the option 'Mark Folder Read'. I'm running TB under Win/XP with all the latest service packs and patches. My TB version: 18.104.22.168 (20081209)
David Marcus - imap folder, or local folder?
Summary: Memory leak / bloat → high Memory usage with 'Mark Folder Read' with thousands of message
David, can you reproduce this with version 2? if you are ready to use version 3 and haven't yet that would be a useful test. suggest using build with latest patches at ftp://ftp.mozilla.org/pub/thunderbird/nightly/latest-comm-1.9.1/ backup your profile before using v3 please also indicate what version and name of mail server
Whiteboard: closeme 2010-02-15
Component: General → Folder and Message Lists
QA Contact: general → folders-message-lists
:( no response, so => incomplete
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.