[Users] [Bug 4157] New: Sudden CPU spike while receiving mail.
noreply at thewildbeast.co.uk
noreply at thewildbeast.co.uk
Sun Feb 17 13:24:28 CET 2019
https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4157
Bug ID: 4157
Summary: Sudden CPU spike while receiving mail.
Classification: Unclassified
Product: Claws Mail
Version: 3.17.3
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Other
Assignee: users at lists.claws-mail.org
Reporter: iivxx at xxvii.st
(Chose 'Other' since I'm unsure what component is causing me trouble).
Sometimes when receiving when Claws-Mail I experience CPU spikes. Occasionally
the program complete freezes, others I'm able to stop it while trying to
navigate the GUI. While I haven't been able to discern a definite pattern I'm
suspect it has something to do with this:
"file-utils.c:58:TIMING safe_fclose : 0s033ms
file-utils.c:133:/usr/bin/shred /home/mrtea/.claws-mail/tmp/claws-crashed
exited with status 0
file-utils.c:133:/usr/bin/shred /home/mrtea/.claws-mail/tmp/tmpfile.00000005
exited with status 0
file-utils.c:133:/usr/bin/shred
/home/mrtea/.claws-mail/mimetmp/00000001.245601_721685.pdf exited with status 0
file-utils.c:133:/usr/bin/shred
/home/mrtea/.claws-mail/mimetmp/0000000a.mimetmp.html exited with status 0
file-utils.c:133:/usr/bin/shred
/home/mrtea/.claws-mail/mimetmp/00000009.mimetmp.html exited with status 0
file-utils.c:133:/usr/bin/shred
/home/mrtea/.claws-mail/mimetmp/00000002.245601_721685.pdf exited with status
0"
This might be complete out of left field, but I can't get the Dillo plugin to
work. Since I can't I just open HTML-messages I just open these in Dillo
externally. While I can't say that it has happened every time, it seems like to
happen more often when I'm using Dillo while receiving e-mail.
I'm on Debian (Stretch) and this seem to have started happening while upgrading
from a previous Claws version. Might have to do with Debian, so I'll provide
more info it proves to be strictly Claws related.
// J.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Users
mailing list