Hi Peter! Am 25.02.20 18:39 schrieb(en) Peter Bloomfield:
If you get a chance, could you get back traces for all threads?
As it's actually easy to reproduce, here is the latest CPU hog: PID USER PR NI VIRT RES SHR S %CPU %MEM ZEIT+ BEFEHL 10327 albrecht 20 0 82,402g 141328 68504 R 99,9 1,7 4:45.36 balsa 10331 albrecht 20 0 82,402g 141328 68504 S 0,0 1,7 0:00.00 gmain 10332 albrecht 20 0 82,402g 141328 68504 S 0,0 1,7 0:00.07 gdbus 10345 albrecht 20 0 82,402g 141328 68504 S 0,0 1,7 0:00.00 dconf worker 12794 albrecht 20 0 82,402g 141328 68504 S 0,0 1,7 0:00.00 BMScavenger 12795 albrecht 20 0 82,402g 141328 68504 S 0,0 1,7 0:00.00 PressureMonitor 12796 albrecht 20 0 82,402g 141328 68504 S 0,0 1,7 0:00.00 HashSaltStorage 12797 albrecht 20 0 82,402g 141328 68504 S 0,0 1,7 0:00.00 ebsiteDataStore 12802 albrecht 20 0 82,402g 141328 68504 S 0,0 1,7 0:00.00 ReceiveQueue The gdb output for all threads is attached. Note that I had /two/ compose dialogues open this time, and I displayed a HTML message before, if this makes any difference. Hope this helps, best, Albrecht.
Attachment:
balsa-cpu-hog
Description: Text document
Attachment:
pgp5aYvtHXusL.pgp
Description: PGP signature