Hi Albrecht,Huh--I really thought I had it!I reproduced one version by starting 
a message, then saving it. On saving, cpu jumped from nothing to 100%. The 
patch fixed that one for me.I can't get to my dev box until next week, so I'll 
write again then.Best,Peter
-------- Original message --------From: Albrecht Dreß <albrecht.dr...@arcor.de> 
Date: 2/28/20  9:47 AM  (GMT-08:00) To: balsa-list@gnome.org Subject: Re: More 
CPU hogging? Hi Peter!Am 27.02.20 00:51 schrieb(en) Peter Bloomfield:> OK, got 
it! Balsa sometimes opens a mailbox just to access a particular message, not to 
display it, and some recent changes did not take that into account. Fixed in 
master and pushed to GitLab. Will rebase gmime3 shortly.Ummm – I /still/ see 
the 100% CPU load when I have composer windows open, using the following git 
version which includes my crypto button patch, though:<snip>commit 
e56f82d3f94f48544edbeda72307553a440e7a6c (HEAD -> master)Merge: 6d8b3460c 
d95c3a90bAuthor: Albrecht Dreß <albrecht.dr...@arcor.de>Date:   Thu Feb 27 
19:11:15 2020 +0100     Merge branch 'master' of 
https://gitlab.gnome.org/GNOME/balsacommit 
d95c3a90b2478e9dcd18d50ba0bf4efd3a10f64b (origin/master, origin/HEAD)Author: 
Peter Bloomfield <peterbloomfi...@bellsouth.net>Date:   Wed Feb 26 18:46:02 
2020 -0500     mailbox-local: Do not pass message to LBMailbox     Do not pass 
message to LibBalsaMailbox for caching, when we're not     preparing a threaded 
view.     * libbalsa/mailbox_local.c (lbm_local_cache_message):</snip>top again 
says:<snip>24708 albrecht  20   0 1174252 122052  55280 R 99,7  1,5   4:40.36 
balsa24712 albrecht  20   0 1174252 122052  55280 S  0,0  1,5   0:00.00 
gmain24713 albrecht  20   0 1174252 122052  55280 S  0,0  1,5   0:00.06 
gdbus24726 albrecht  20   0 1174252 122052  55280 S  0,0  1,5   0:00.00 dconf 
worker</snip>The gdb output is attached.BTW, the 100% cpu I observe right now 
seems to be related to the dialogue composing this message.  When I hit send, 
this shows pinentry as to unlock my crypto token storing my private GPG key.  
And as soon as pinentry appears, the CPU load of Balsa goes to 0!  Cancel 
pinentry bings bach the 100% CPU load…  Strange!Unless this is related to the 
crypto button patch (although I don't see where it should interfere, to be 
honest) there still seems to be a different problem.Anything else I could 
test?Best,Albrecht.
_______________________________________________
balsa-list mailing list
balsa-list@gnome.org
https://mail.gnome.org/mailman/listinfo/balsa-list

Reply via email to