Re: More CPU hogging?

Albrecht Dreß <[email protected]> Fri, 28 Feb 2020 18:46:47 +0100
Newsgroups gmane.comp.gnome.apps.balsa
Message-ID <[email protected]>
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 d95c3a90b
Author: Albrecht Dreß <[email protected]>
Date:   Thu Feb 27 19:11:15 2020 +0100

     Merge branch 'master' of https://gitlab.gnome.org/GNOME/balsa

commit d95c3a90b2478e9dcd18d50ba0bf4efd3a10f64b (origin/master, origin/HEAD)
Author: Peter Bloomfield <[email protected]>
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 balsa
24712 albrecht  20   0 1174252 122052  55280 S  0,0  1,5   0:00.00 gmain
24713 albrecht  20   0 1174252 122052  55280 S  0,0  1,5   0:00.06 gdbus
24726 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
[email protected]
https://mail.gnome.org/mailman/listinfo/balsa-list
signature.asc (application/pgp-signature, 488 B)
-----BEGIN PGP SIGNATURE-----

iQEzBAABCgAdFiEEcCEPemLFTtyGf4zATKlvDmfn2fgFAl5ZUgcACgkQTKlvDmfn
2fjnTAgA0T7ul6P2d9txcct+COJxlqlI0ZZEXqESMRHBT7CSqyyGWJt8MOn8JUNR
lvfLFlL5Pyg0zKsQMvBgzpng9LvP2bTc8BMNd8Uoo+cYn7Q+6CkGULktgIPkZqBX
3JSKfpCZDfAkgCnOl3ogfKkSTPWmfqKKb0rKKMEEWgrTeOOKrLr4wTLCRuhLtz66
yIGYeTFyauGsoTC4JO4FW4VbQIS9cxJ09wkRM8j5M8oKcWHLmcqanHns/NLVKXhv
VfvNkmDgJvslx7CBzRXfG6E898Qv5p1oK2SzBoinb7kHwT9NlaOcjihRCR9ZLBBB
MszGwcKSTbtPREddWgd2YFjkXXWOCA==
=IORQ
-----END PGP SIGNATURE-----