Bug 1135709

Created attachment 932960 [details]
File: backtrace

Created attachment 932961 [details]
File: cgroup

Created attachment 932962 [details]
File: core_backtrace

Created attachment 932963 [details]
File: dso_list

Created attachment 932964 [details]
File: environ

Created attachment 932965 [details]
File: exploitable

Created attachment 932966 [details]
File: limits

Created attachment 932967 [details]
File: maps

Created attachment 932968 [details]
File: open_fds

Created attachment 932969 [details]
File: proc_pid_status

Created attachment 932970 [details]
File: var_log_messages

Thanks for a bug report. Is this reproducible with that particular message, please? I see from the backtrace that this happened when the images referenced in a HTML part of the message were downloading. To let evolution download them again you might delete ~/.cache/evolution/http/ folder first. It would help if you could share the message, if it contains any private information, then either delete (replace) it there, or just sent the zipped message to me directly, just mention the bug reference in the subject, thus it'll not left unnoticed in my spam folder. Thanks in advance.

No, the message that triggered it had been half-deleted when I looked to try to reproduce it. It still showed in the message index, but trying to view it gave a message that it was no longer there(?).

Is it deleted from the server too? What is the exact error message?

Also, does evolution console show anything useful, when you select the message?

I'm afraid the message is gone altogether.

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

This, or something very like it, just happened again. I had a message window open, and it appeared to stop responding: I couldn't scroll the message.

When evolution crashed I tried to report the crash with abrt but the crash had disappeared, I guess because of this:

Oct 02 17:35:54 rubik abrt-hook-ccpp[9525]: Saved core dump of pid 12745 (/usr/bin/evolution) to /var/tmp/abrt/ccpp-2014-10-02-17:35:41-12745 (1527869440 bytes)
[...]
Oct 02 17:36:29 rubik abrt-hook-ccpp[9699]: Saved core dump of pid 9679 (/usr/libexec/tracker-extract) to /var/tmp/abrt/ccpp-2014-10-02-17:36:29-9679 (122191872 bytes)
Oct 02 17:36:29 rubik abrt-hook-ccpp[9699]: /var/tmp/abrt is 1650397080 bytes (more than 1279MiB), deleting 'ccpp-2014-10-02-17:35:41-12745'

I still have the message, but I cannot reproduce the problem now.

I do have the messages from evolution that ended up in the system journal. I'll attach those.

Created attachment 943491 [details]
evolution-logs.txt.xz

Trimmed output of "journalctl -b 0 _COMM=evolution > evolution-logs.txt" to include only the run that crashed.

Hmm, you are getting many (semi) interesting runtime warnings on a console.
This time evolution crashed with:
> *** Error in `evolution': double free or corruption (out):
> 0x00007fd20cbaf820 ***
> ....
> lib64/libgobject-2.0.so.0(g_object_unref+0xfc)[0x3ec6214cac]
> /usr/lib64/evolution/3.12/libevolution-mail.so(+0x3b196)[0x7fd30c44e196]

Which may or may not be the same issue as the original report. In any case there is happening something odd, the memory corruption, but I do not know why, what the cause is. Maybe it's that a certain type of message is triggering it, and then evolution crashes on a completely unrelated place. These things are hard to debug (as always).

Could you try to watch the messages for some pattern, like for example only HTML messages with remote images are causing memory corruption? The initial crash happened when a remote image was about to be downloaded. I do not see whether you load images from the Internet on demand/never, always or when the sender is in your addressbook.

I get e.g.

(evolution:14353): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed

as soon as I delete a message, and it happens nearly every time I perform any action (delete a message, select messages, switch folder etc).

After only reading mail for a minute or so I get this:

(evolution:14353): GLib-CRITICAL **: Source ID 9651 was not found when attempting to remove it

It makes it hard to spot patterns for all the noise. :-) Am I the only one seeing these messages? If so I can file a separate bug report if you like.

(In reply to Tim Waugh from comment #21)
> Am I the only one seeing these messages?

No no, the first is from webkitgtk3, it's known and filled upstream [1]. The second is rather harmless and might to do something with the activities shown in the status bar. GLib didn't claim these issues in earlier versions, thus it was "not known". Either of these should not have much impact on the main behaviour, though (at least in theory).

[1] https://bugs.webkit.org/show_bug.cgi?id=127474

This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.