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 543345 - Evolution freezing
Evolution freezing
Status: RESOLVED DUPLICATE of bug 558737
Product: evolution
Classification: Applications
Component: Mailer
2.22.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-07-16 21:59 UTC by Matěj Cepl
Modified: 2008-11-05 11:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22

Attachments
backtrace from gdb (45.71 KB, text/plain)
2008-07-16 22:01 UTC, Matěj Cepl 		Details

Description Matěj Cepl 2008-07-16 21:59:45 UTC 
<mcepl> mbarnes: ping -- reporting one frozen Evolution (it would make me almost a creationist ;-)) -- backtrace is attached. Any thoughts? (it is Fedora 9, fully updated, evolution-2.22.3.1-1.fc9.i386).
<mbarnes> mcepl: looks like a mutex deadlock in camel  (of course it would be camel)
<mcepl> mbarnes: should I file a bug?
<mbarnes> mcepl: may be hard to reproduce, but go ahead and file a bug
Comment 1 Matěj Cepl 2008-07-16 22:01:24 UTC 
Created attachment 114683 [details]
backtrace from gdb
Comment 2 Akhil Laddha 2008-07-17 04:41:00 UTC 
Pasting traces from comment#1 

Loaded symbols for /usr/lib/gconv/KOI8-R.so
Reading symbols from /usr/lib/gconv/CP1252.so...Reading symbols from /usr/lib/debug/usr/lib/gconv/CP1252.so.debug...done.
done.
Loaded symbols for /usr/lib/gconv/CP1252.so
0x00110416 in __kernel_vsyscall ()
thread apply all backtrace: No such file or directory.
quit: No such file or directory.
Missing separate debuginfos, use: debuginfo-install avahi.i386 gnome-pilot.i386 gnome-spell.i386 gtk2-engines.i386 pilot-link.i386
(gdb) thread appply [K[K[K[K[Kl[Kply all backtrace

+ Trace 203038







Comment 3


Milan Crha





          2008-10-01 17:19:32 UTC
        



What a nice coincidence.

Thread 5 is waiting for the connect_lock, same as Thread 3 and Thread 2.
Thread 4 doesn't show correct line numbers, which is quite bad. Because of broken line numbers, the Thread 4 is probably holding the connect_lock (there left noone else). Even I believe none of the other threads is holding the cache_lock, it seems that someone is holding it...






Comment 4


Milan Crha





          2008-11-05 11:44:46 UTC
        



Marking this as a duplicate of the other bug because the newer one has a patch.

*** This bug has been marked as a duplicate of 558737 ***