After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 613181 - Mistakenly removed statement
Mistakenly removed statement
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
2.30.x (obsolete)
Other Linux
: Normal major
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
: 607911 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2010-03-17 19:20 UTC by Reid Thompson
Modified: 2013-09-13 01:07 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
email in question (306.53 KB, message/rfc822)
2010-03-17 19:20 UTC, Reid Thompson
  Details
stacktrace of evolution while in unresponsive state (29.59 KB, application/octet-stream)
2010-03-17 19:22 UTC, Reid Thompson
  Details
gtkhtml patch (502 bytes, patch)
2010-03-18 14:52 UTC, Milan Crha
committed Details | Review

Description Reid Thompson 2010-03-17 19:20:51 UTC
Created attachment 156391 [details]
email in question

Re-sending, as original doesn't appear to have made it to the mailing list.
Also filing a bug as testing after a git head rebuild does not remedy it.

As info -- and in case anyone else wants to validate/invalidate.

Using evo git head built ~10 AM yesterday.  Attached email is downloaded via fetchmail and placed into an evo maildir account.  Selecting the email in evo causes evo cpu usage on dual core core 2 to consume 50% of all available cpu and causes memory usage consumed by evo to start increasing continuously.  Evo becomes unresponsive (system pretty much does also).  Status bar states that it is Formatting message (0% complete)
Result is evo must be killed.

Not sure if it's just pertinent to my setup or not.  I'll flush and rebuild and see if the issue persists.
Comment 1 Reid Thompson 2010-03-17 19:22:29 UTC
Created attachment 156392 [details]
stacktrace of evolution while in unresponsive state
Comment 2 Milan Crha 2010-03-18 14:32:02 UTC
Confirming, it makes evo busy for me too.
Comment 3 Milan Crha 2010-03-18 14:52:53 UTC
Created attachment 156458 [details] [review]
gtkhtml patch

for gtkhtml;

It happened here:
http://git.gnome.org/browse/gtkhtml/commit/?h=gnome-2-30&id=16c2ce11376f62f3d3f9324fc5b5e73f71571169
and it turned out that it's not as that much a death assignment.
Comment 4 Lucian Langa 2010-03-18 14:56:26 UTC
*** Bug 607911 has been marked as a duplicate of this bug. ***
Comment 5 Matthew Barnes 2010-03-18 16:10:06 UTC
Does "git blame" reveal anything about why that line was commented in the first place?
Comment 6 Milan Crha 2010-03-18 17:10:07 UTC
That's (git blame) how I found you commented it out. :) I'm asking for an approval for committing this change before 2.30, to have happy users.
Comment 7 Matthew Barnes 2010-03-18 18:20:34 UTC
D'oh!  I bet it was part of my "dead assignments" cleanup.

Commit it.
Comment 8 Matthew Barnes 2010-03-18 18:22:42 UTC
You'll want to request a code freeze exception from the release team for gnome-2-30.  I'm sure they'll approve, but need to follow the process.
Comment 9 Milan Crha 2010-03-19 18:29:57 UTC
Created commit 6a21276 in gtkhtml master (3.31.1+)
Created commit cfe0026 in gtkhtml gnome-2-30 (3.30.0+)