![]() ![]() > When (A) occurs, NNN of "periodic check of cached dbs, count=NNN" is declines. > (A-2) And, after a while, memory resources for the msgDB object is purged by garbage collector. > (A-1) msgDB is completely closed sooner or later and xxx.msf is written back/closed by cachedDB management process. > (A) If no one accessed DB after setting msgFolder.msgDabase=null, > i.e, # of opened DB is reduced to mail.db.max_open(default=30) at phase (2). > (2-2) If # of still opened DB exceeds mail.db.max_open(default=30), msgFolder.msgDabase=null is set. > (2-1) Report "open db count MMM" where MMM is still opened DB count after phase (1). > (1-3) if msgDB is opened before idle_limit milliseconds, store msgFolder.msgDabase=null(reduce 1 from reference count to msgDB) > This is reported by "skipping cachedDB not open in folder: Gesendet". > (1-2) If cached DB is not opened(msgFolder.msgDabase=null is already set), nothing is done on it, > This is reported by log of "folder open in window, name: Posteingang" in phase (1)/(2). > If msgDB is for folder which is currently selected at folder pane, close at phase (1)/(2) is skipped. > where NNN is # of msgDBs which was opened by someone(xxx.msf was read) at least once and was cached. > (1-1) Report "periodic check of cached dbs, count=NNN" What is done by checkCachedDBs every 1 minute is: Only open it after X hours if there is significant CPU activity while idle. Please do the test again, but do not have the Error console open. ![]() > but goes down to 0.1% when it is in the background or unused in the > Thunderbird uses up to >70% CPU when I use the ui (just scroll up and down), No, if you have only 6 active folders I cannot understand the background work yet. > The next minute it is again down to "periodic check of cached dbs, count=6". Below you say it is around 6-7 every minute. It would explain the CPU use if you had >30 databases open all the time and every minute TB tried to get them down to 30. > 17:50:45 INFO periodic check of cached ![]() > 17:43:45 INFO periodic check of cached > Now something like this appears every minute: > I restored mail.db.idle_limit to 300.000, mail.db.max_open is 30, I In the log it is "periodic check of cached dbs, count=6" every minute.Īny ideas what I could do to come closer to the problem? Now Thunderbird is constantly at 5-8% CPU even when it is in the background. Thunderbird uses up to >70% CPU when I use the ui (just scroll up and down), but goes down to 0.1% when it is in the background or unused in the foreground. The next minute it is again down to "periodic check of cached dbs, count=6". 17:50:45 ĝEBUG skipping cachedDB not open in folder: 2001 17:50:45 ĝEBUG skipping cachedDB not open in folder: Archiv 17:50:45 INFO periodic check of cached dbs, count=98 17:43:45 ĝEBUG skipping cachedDB not open in folder: Papierkorb 17:43:45 ĝEBUG skipping cachedDB not open in folder: Gesendet 17:43:45 ĝEBUG folder open in window, name: Posteingang 17:43:45 INFO periodic check of cached dbs, count=9 Now something like this appears every minute: I restored mail.db.idle_limit to 300.000, mail.db.max_open is 30, I restarted thunderbird. > Thank you for this great product and for answering to user problems! Other bugs which mention the preference (but not all of those bugs have the *this* problem - they just mention the preference) ![]() Can you find (with taskmgr or other tools) the running thunderbird.exe has characteristics other than high CPU - for example higher memory usage or higher IO under similar workload - compared to when you have changed the preference?ģ. does your problem reproduce if you reset the preference and have thunderbird started in safe mode?Ģ. I am too tired at the moment to give much coherent advice, but get you some info and get the ball rolling to figure this out.ġ. Unfortunately you are not the first person to observe this. > I increased mail.db.idle_limit as suggested in > Monitor showed Thunderbird using ~30% CPU regularly. > My battery life got somewhat shorter, the macbook warmer, and the Activity Quote "As of version 38, most issues involving mail.db.idle_limit should be resolved." Note the word "most". Wayne claimed, that these issues should be resolved as of version 38. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |