Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#5931 - evolution 2.8 dies, tries to take down system
Attached to Project:
Arch Linux
Opened by Evan Klitzke (eklitzke) - Monday, 04 December 2006, 14:45 GMT
Last edited by Jan de Groot (JGC) - Sunday, 22 April 2007, 21:47 GMT
Opened by Evan Klitzke (eklitzke) - Monday, 04 December 2006, 14:45 GMT
Last edited by Jan de Groot (JGC) - Sunday, 22 April 2007, 21:47 GMT
|
DetailsRight now I am using the current evolution package (2.8.1-2). and I am stuck on an email in evolution, where every time I open evolution the following two things happen:
1) CPU usage goes to 100% 2) Evolution starts allocating memory as fast as it can This is the first time I have had this happen in Arch (although I am a new user), but I once saw this same thing happen to my roommate, who came back to his computer to find that Evolution was using all the RAM and CPU time on his computer. This was on whatever version of Evolution is packaged for Ubuntu Edgy Eft (also 2.8.something), so it appears to be an upstream issue. If it helps, the error first occurred when I searched for LogWatch emails in the current directory, and then selected such an email. It would appear that there is a bug in Evolution's parser that causes it to choke on the unusual formatting of these emails. If I click on a folder in another email account and force quite Evolution before all my RAM is used, I will be in the new folder when re-opening Evolution. But when I switch back to the folder for the email account I am trying to access, the old email is highlighted and the problem re-occurs. |
This task depends upon
Does this seem like your bug? http://bugzilla.gnome.org/show_bug.cgi?id=273171
12:29 < eck> what is the best way to file a bug report if Evolution floors the CPU and starts allocating
all my ram as fast as it can? it happened this morning consistently on the same email, and
if it happens again I want to be able to file a bug report
12:29 <@guenther> Is it a large mail?
12:29 <@guenther> couple MBytes text?
12:29 < eck> guenther: yes, it was a large log
12:29 -!- cortana [~sam@62-31-146-25.cable.ubr12.azte.blueyonder.co.uk] has joined #evolution
12:30 <@guenther> In that case...
12:30 <@guenther> Don't file it.
12:30 <@guenther> That's the best way to "file this issue". ;)
12:30 < eck> is this a known bug?
12:30 <@guenther> It's known, and there at least is a hack-ish workaround already.
12:31 < eck> if I set up a filter to forward the email elsewhere and delete it, do you know if that will
prevent evolution from dying on me?
12:32 <@guenther> yes
12:32 <@guenther> and yes
12:32 <@guenther> The issue is rendering that mail,
12:32 <@guenther> So, if you do not view it, you are perfectly fine.
12:32 < eck> ok, thanks
12:32 <@guenther> Remember that you can view "marked for deletion" mails, too. :)
"Evolution cannot render this email as it is too large to handle. You can view it unformatted or with an external text editor."