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 458549 - Crash in e_cal_backend_get_object_list at e-cal-backend.c:786
Crash in e_cal_backend_get_object_list at e-cal-backend.c:786
Status: RESOLVED INCOMPLETE
Product: evolution-data-server
Classification: Platform
Component: Calendar
1.10.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-07-20 06:50 UTC by Allan Engelhardt
Modified: 2011-11-24 06:04 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Attachments
Stack trace from the main (frozen) client (3.36 KB, text/plain)
2007-07-20 06:54 UTC, Allan Engelhardt
Details

Description Allan Engelhardt 2007-07-20 06:50:15 UTC
Steps to reproduce:
Another "I just left evolution running" overnight crash.  There has got to be a memory/thread corruption somewhere.



Stack trace:
System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 586641408 vsize: 586641408 resident: 72638464 share: 6938624 rss: 72638464 rss_rlim: 18446744073709551615
CPU usage: start_time: 1184852632 rtime: 814 utime: 779 stime: 35 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/libexec/evolution-data-server-1.10'

Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 46912631602128 (LWP 27214)]
[New Thread 1147435344 (LWP 22107)]
[New Thread 1136945488 (LWP 27253)]
[New Thread 1074006352 (LWP 27215)]
0x00002aaab003d18f in __libc_waitpid (pid=22108, stat_loc=0x7fff8a3cd47c, 
    options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41
41	  int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);

Thread 2 (Thread 1147435344 (LWP 22107))

  • #0 __lll_mutex_lock_wait
    from /lib64/libpthread.so.0
  • #1 _L_mutex_lock_103
    from /lib64/libpthread.so.0
  • #2 __pthread_mutex_lock
    at pthread_mutex_lock.c line 81
  • #3 gnome_segv_handler
    at server.c line 97
  • #4 <signal handler called>
  • #5 e_cal_backend_get_object_list
  • #6 ORBit_small_invoke_adaptor
    at orbit-small.c line 844
  • #7 ORBit_POAObject_handle_request
    at poa.c line 1351
  • #8 ORBit_POAObject_invoke_incoming_request
    at poa.c line 1421
  • #9 giop_thread_queue_process
    at giop.c line 771
  • #10 giop_request_handler_thread
    at giop.c line 481
  • #11 g_thread_pool_thread_proxy
    at gthreadpool.c line 265
  • #12 g_thread_create_proxy
    at gthread.c line 591
  • #13 start_thread
    at pthread_create.c line 296
  • #14 clone
    from /lib64/libc.so.6


----------- .xsession-errors (23084 sec old) ---------------------
Turning an undo...
Turning an undo...
Turning an undo...
Turning an undo...
Turning an undo...
Turning an undo...
Turning an undo...
Turning an undo...
Turning an undo...
Turning an undo...
Turning an undo...
Turning an undo...
Turning an undo...
Turning an undo...
Turning an undo...
--------------------------------------------------

Other information:
evolution-data-server-1.10.3-1.fc7 on Fedora 7 x86_64
Comment 1 Allan Engelhardt 2007-07-20 06:54:28 UTC
Created attachment 92025 [details]
Stack trace from the main (frozen) client

The Evolution client GUI was frozen.  On the off chance that this may be useful to somebody, I have attached a stack trace from the running client.

I wonder if this happens at midnight when it changes from one day to another?
Comment 2 Allan Engelhardt 2007-07-21 15:15:09 UTC
For the client stack trace see also Bug 459001 which is an instance where the client hangs at the same place but the data server is still running.
Comment 3 Allan Engelhardt 2007-08-03 06:29:59 UTC
Slightly different version of what appears to be the same problem; this stack trace more clearly suggesting that this is a memory problem (see the libc_free signal at malloc.c:3593 in the first back trace).

Again, this was an overnight crash.

---------------------------------------------

System: Linux 2.6.22.1-27.fc7 #1 SMP Tue Jul 17 17:19:58 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 610820096 vsize: 610820096 resident: 53264384 share: 8826880 rss: 53264384 rss_rlim: 18446744073709551615
CPU usage: start_time: 1186043856 rtime: 774 utime: 745 stime: 29 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/libexec/evolution-data-server-1.10'

Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 46912631602128 (LWP 8169)]
[New Thread 1147435344 (LWP 2176)]
[New Thread 1105475920 (LWP 2174)]
[New Thread 1126455632 (LWP 8210)]
[New Thread 1074006352 (LWP 8170)]
0x00002aaab003d18f in __libc_waitpid (pid=2177, stat_loc=0x7fff434e0afc, 
    options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41
41	  int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);

Thread 2 (Thread 1147435344 (LWP 2176))

  • #0 __lll_mutex_lock_wait
    from /lib64/libpthread.so.0
  • #1 _L_mutex_lock_103
    from /lib64/libpthread.so.0
  • #2 __pthread_mutex_lock
    at pthread_mutex_lock.c line 81
  • #3 gnome_segv_handler
    at server.c line 97
  • #4 <signal handler called>
  • #5 e_cal_backend_get_object_list
  • #6 ORBit_small_invoke_adaptor
    at orbit-small.c line 844
  • #7 ORBit_POAObject_handle_request
    at poa.c line 1351
  • #8 ORBit_POAObject_invoke_incoming_request
    at poa.c line 1421
  • #9 giop_thread_queue_process
    at giop.c line 771
  • #10 giop_request_handler_thread
    at giop.c line 481
  • #11 g_thread_pool_thread_proxy
    at gthreadpool.c line 265
  • #12 g_thread_create_proxy
    at gthread.c line 594
  • #13 start_thread
    at pthread_create.c line 296
  • #14 clone
    from /lib64/libc.so.6


----------- .xsession-errors (20756 sec old) ---------------------
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4e00376 specified for 0x4e00378 (xine Panel).
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4c00003 (Evince Doc)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Liferea did receive signal 11 (Segmentation fault).
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
...Too much output, ignoring rest...
--------------------------------------------------
Comment 4 Akhil Laddha 2011-10-11 09:51:38 UTC
Can you please check again whether this issue still happens in Evolution 3.0.3 or 3.2.0 and update this report by adding a comment and changing the "Version"
field? Thanks a lot.
Comment 5 Akhil Laddha 2011-11-24 06:04:09 UTC
Please feel free to reopen the bug if the problem still occurs with a newer
version of Evolution.