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 661353 - [abrt] Memory corruption under folder_changed_change, camel_folder_search_search
[abrt] Memory corruption under folder_changed_change, camel_folder_search_search
Status: RESOLVED OBSOLETE
Product: evolution-data-server
Classification: Platform
Component: Mailer
3.2.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2011-10-10 07:00 UTC by Milan Crha
Modified: 2015-03-10 16:57 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Milan Crha 2011-10-10 07:00:15 UTC
Moving this from a downstream bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=744469

libreport version: 2.0.6
abrt_version:   2.0.4.981
backtrace_rating: 4
cmdline:        evolution
comment:        My laptop went to sleep after one hour of being idle, and
evolution crashed as soon as I woke the machine up.
crash_function: _int_memalign
executable:     /usr/bin/evolution
kernel:         3.1.0-0.rc8.git0.1.fc16.x86_64
reason:         Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
time:           Sat Oct  8 21:12:39 2011

Core was generated by `evolution'.
Program terminated with signal 11, Segmentation fault.

Thread 5 (Thread 0x7f43d59bf700 (LWP 1845))

  • #0 read
    at ../sysdeps/unix/syscall-template.S line 82
  • #1 read
    at /usr/include/bits/unistd.h line 45
  • #2 unix_signal_helper_thread
    at gmain.c line 4567
  • #3 g_thread_create_proxy
    at gthread.c line 1962
  • #4 start_thread
    at pthread_create.c line 305
  • #5 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 115

Comment 1 Milan Crha 2012-10-22 09:57:56 UTC
Another similar downstream bug report from 3.4.4:
https://bugzilla.redhat.com/show_bug.cgi?id=868691

It's similar, because the lower part of the crashing thread is the same, which the memory corruption was "discovered" in a different point of the crash. I guess this should be fine in 3.6.1.


Thread 1 (Thread 0x7f1c1d5f2700 (LWP 9775))

  • #0 __GI_raise
    at ../nptl/sysdeps/unix/sysv/linux/raise.c line 64
  • #1 __GI_abort
    at abort.c line 91
  • #2 __libc_message
    at ../sysdeps/unix/sysv/linux/libc_fatal.c line 198
  • #3 malloc_printerr
    at malloc.c line 5027
  • #4 _int_malloc
    at malloc.c line 3811
  • #5 __GI___libc_malloc
    at malloc.c line 2928
  • #6 g_realloc
    at gmem.c line 224
  • #7 g_ptr_array_maybe_expand
    at garray.c line 1093
  • #8 g_ptr_array_add
    at garray.c line 1350
  • #9 camel_folder_search_search
  • #10 local_folder_search_by_uids
  • #11 camel_folder_search_by_uids
  • #12 folder_changed_change
    at camel-vee-folder.c line 422
  • #13 vee_folder_process_changes
    at camel-vee-folder.c line 661
  • #14 session_do_job_cb
    at camel-session.c line 165
  • #15 run_in_thread
    at gsimpleasyncresult.c line 861
  • #16 io_job_thread
    at gioscheduler.c line 177
  • #17 g_thread_pool_thread_proxy
    at gthreadpool.c line 309
  • #18 g_thread_proxy
    at gthread.c line 801
  • #19 start_thread
    at pthread_create.c line 309
  • #20 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 115

Comment 2 Milan Crha 2015-03-10 16:57:52 UTC
No duplicate for a long time, I'm closing this.