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 604959 - Crash in camel_message_info_free()
Crash in camel_message_info_free()
Status: RESOLVED OBSOLETE
Product: evolution-data-server
Classification: Platform
Component: Mailer
2.28.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-12-18 22:48 UTC by dan.mcdonald
Modified: 2013-08-23 18:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description dan.mcdonald 2009-12-18 22:48:32 UTC
What were you doing when the application crashed?
deleting a large number of messages from several search folders in rapid succession.

Hopefully the 9 debug packages are sufficient, if not, please tell me which addional ones to load.


Distribution: Mandriva Linux release 2010.0 (Official) for i586
Gnome Release: 2.28.0 2009-12-16 (Mandriva)
BugBuddy Version: 2.28.0

System: Linux 2.6.31.6-desktop-1mnb #1 SMP Tue Dec 8 16:20:45 EST 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10601000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Ia Ora Steel
Icon Theme: gnome
GTK+ Modules: canberra-gtk-module, gnomebreakpad

Memory status: size: 264564736 vsize: 264564736 resident: 103821312 share: 24367104 rss: 103821312 rss_rlim: 18446744073709551615
CPU usage: start_time: 1261157807 rtime: 87960 utime: 82492 stime: 5468 cutime:1 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution'

[?1034h[Thread debugging using libthread_db enabled]
[New Thread 0xb5af88f0 (LWP 16032)]
[New Thread 0xa8ffeb70 (LWP 30161)]
[New Thread 0xa75fab70 (LWP 30046)]
[New Thread 0xaf311b70 (LWP 30043)]
[New Thread 0xaf357b70 (LWP 21586)]
[New Thread 0xaa9ffb70 (LWP 21585)]
[New Thread 0xae2c6b70 (LWP 16103)]
[New Thread 0xad204b70 (LWP 16102)]
[New Thread 0xb0311b70 (LWP 16059)]
[New Thread 0xb0b12b70 (LWP 16058)]
[New Thread 0xb21fdb70 (LWP 16057)]
[New Thread 0xb29feb70 (LWP 16056)]
[New Thread 0xb31ffb70 (LWP 16052)]
[New Thread 0xb45afb70 (LWP 16050)]
[New Thread 0xb4db0b70 (LWP 16049)]
0xffffe424 in __kernel_vsyscall ()

Thread 3 (Thread 0xa75fab70 (LWP 30046))

  • #0 __kernel_vsyscall
  • #1 __lll_lock_wait
    from /lib/i686/libpthread.so.0
  • #2 _L_lock_657
    from /lib/i686/libpthread.so.0
  • #3 pthread_mutex_lock
    from /lib/i686/libpthread.so.0
  • #4 <signal handler called>
  • #5 pthread_mutex_lock
    from /lib/i686/libpthread.so.0
  • #6 camel_message_info_free
    at camel-folder-summary.c line 4514
  • #7 free_message_info
    at camel-folder.c line 1027
  • #8 camel_folder_free_message_info
    at camel-folder.c line 1044
  • #9 camel_folder_thread_messages_unref
    at camel-folder-thread.c line 723
  • #10 camel_folder_search_search
  • #11 search_by_expression
  • #12 camel_folder_search_by_expression
  • #13 vee_search_by_expression
  • #14 camel_folder_search_by_expression
  • #15 regen_list_exec
    at message-list.c line 4041
  • #16 mail_msg_proxy
    at mail-mt.c line 522
  • #17 g_thread_pool_thread_proxy
    at gthreadpool.c line 265
  • #18 g_thread_create_proxy
    at gthread.c line 635
  • #19 start_thread
    from /lib/i686/libpthread.so.0
  • #20 clone
    from /lib/i686/libc.so.6

Comment 1 Milan Crha 2010-02-16 15:32:18 UTC
Maybe fixed by bug #574940, as it's using the same code.
Comment 2 Matthew Barnes 2013-08-23 18:05:42 UTC
Closing as OBSOLETE since the stack trace is too old to be useful now.

Reopen the bug and update the version field if this crash still occurs in Evolution 3.8 or later.