Discussions of development and use of the Sup email client
 help / color / mirror / Atom feed
From: Tero Tilus <tero@tilus.net>
To: supmua <supmua@googlegroups.com>
Subject: Re: [sup] Excessive CPU Usage
Date: Sat, 16 Jan 2016 14:21:55 +0200	[thread overview]
Message-ID: <1452945939-sup-8006@tilus.net> (raw)
In-Reply-To: <1452785218-sup-8775@localhost.localdomain>

Willem, 2016-01-14 17:55:
> 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

Report the issue in https://github.com/sup-heliotrope/sup/issues and
attach the offending email (save raw message as file).  Then others
are able to try reproducing and debugging the issue.

-- 
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/


      reply	other threads:[~2016-01-16 12:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-14 15:55 Willem
2016-01-16 12:21 ` Tero Tilus [this message]

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=1452945939-sup-8006@tilus.net \
    --to=tero@tilus.net \
    --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