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 344382 - Evolution locked up and mangled its cache
Evolution locked up and mangled its cache
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Mailer
2.4.x (obsolete)
Other other
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-06-09 11:53 UTC by Fabian Fagerholm
Modified: 2010-04-29 01:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Attachments
Tar archive of the broken folder (86.32 KB, application/x-bzip)
2006-06-09 11:55 UTC, Fabian Fagerholm
Details

Description Fabian Fagerholm 2006-06-09 11:53:01 UTC
Distribution: Debian testing/unstable
Package: Evolution
Severity: Normal
Version: GNOME2.14.1 2.4.x
Gnome-Distributor: Debian
Synopsis: Evolution locked up and mangled its cache
Bugzilla-Product: Evolution
Bugzilla-Component: Mailer
Bugzilla-Version: 2.4.x
Description:
Description of Problem:
I was using Evolution normally. Suddenly it locked up and started
consuming 100% CPU time. An IMAP folder was open at the time. Looking
with strace, the process did not make any system calls, it was just
spinning in its own code (no strace output). I killed it and restarted
it. Since Evolution opens the same folder that was open before, the same
thing immediately happened: the UI froze and Evolution consumed 100% CPU
time. I killed it, and tried starting it with various command line
options. Specifying --offline didn't help, because the folder is opened
from the cache. Specifying --component=calendar allowed me to use the
calendar normally, but when switching to mail, the lockup immediately
occurred.

Eventually, I deleted all the files in .evolution/mail/imap/[my
account]/folders/INBOX/subfolders/Lists/subfolders/Debian/subfolders/DebConf/subfolders/Video
which was the "broken" folder. Upon starting Evolution, everything
worked fine, the messages were downloaded again from the server and the
cache directory was again filled with messages.




------- Bug created by bug-buddy at 2006-06-09 11:53 -------

Comment 1 Fabian Fagerholm 2006-06-09 11:55:37 UTC
Created attachment 67034 [details]
Tar archive of the broken folder

I saved the contents of the cache directory and made this tar.bz2, in case it would ease debugging.

The exact Evolution version was 2.4.2.1.
Comment 2 André Klapper 2006-06-09 12:50:21 UTC
Just for your interest, if it is the Mailer component crashing, a common cause is a particular mail that crashes while being rendered. To prevent rendering of the mail, you can disable the preview pane and set the message display to 'source', which will display the raw message.

Disable the preview pane:
$ gconftool-2 --set /apps/evolution/mail/display/show_preview --type bool 0

Display the raw source message:
$ gconftool-2 --set /apps/evolution/mail/display/message_style --type int 2
Comment 3 Fabian Fagerholm 2006-06-09 14:42:57 UTC
Andre, thanks for the hint!

If I understand your description correctly, the Mailer component should crash every time on the same message, regardless of whether or not the message comes from the cache or is downloaded fresh from the IMAP server.

In this case, the lockup disappeared when manually emptying the cache, as described above. The same emails were, however, re-downloaded from the IMAP server later, and displayed fine after that. So I think this is a different bug.

There is also ongoing discussion in the Debian BTS on two similar bugs, see here:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=295270
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=347703
Comment 4 André Klapper 2010-03-13 23:56:19 UTC
I assume that this can be closed as OBSOLETE nowadays, or is this still an issue in a recent version of Evolution?
Comment 5 Tobias Mueller 2010-04-29 01:03:06 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!