From: Willem <willvdw@gmail.com>
To: supmua <supmua@googlegroups.com>
Cc: eg <eg@gaute.vetsj.com>
Subject: Excessive CPU Usage
Date: Thu, 14 Jan 2016 16:55:31 +0100 [thread overview]
Message-ID: <1452785218-sup-8775@localhost.localdomain> (raw)
Hi fellow sup fans!!
I have used sup off and on for a few years already, depending on computers and work situation; and keep coming back because it really is the best email tool I have found for my email needs!!
Now I have just completed a fresh multi-account install of sup-mail 0.20.0-1 on Debian 8.2.0 which runs beautifully after some initial hassles.
However the one problem I have is that sup works fine when reading and archiving emails then without warning the processing becomes super slow. I have checked CPU usage and found that on certain fairly random and innocent looking emails the usage shoots up to 100% and stays there until I quit sup and re-start it. Then if I go back to the same email that caused the problem, the CPU usage shoots up when I attempt to open it.
Any suggestions or ideas what I should do about sorting this problem out would be greatly appreciated - thanks
Cheers
Willem
next reply other threads:[~2016-01-14 15:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 15:55 Willem [this message]
2016-01-16 12:21 ` [sup] " Tero Tilus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1452785218-sup-8775@localhost.localdomain \
--to=willvdw@gmail.com \
--cc=eg@gaute.vetsj.com \
--cc=supmua@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox