Bug 274307 – started evolution with focus on personal address book having 1000 contacts. Selected another personal address book - EDS crashed

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 274307 - started evolution with focus on personal address book having 1000 contacts. Selected another personal address book - EDS crashed


Summary:	started evolution with focus on personal address book having 1000 contacts. S...


Status:	RESOLVED INCOMPLETE

Product:	evolution-data-server
Classification:	Platform
Component:	Contacts
Version:	1.2.x (obsolete)
Hardware:	Other All

Importance:	Normal major
Target Milestone:	---
Assigned To:	evolution-addressbook-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:	327516

Reported:	2005-04-01 12:46 UTC by Nagappan Alagappan
Modified:	2013-09-14 16:48 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Nagappan Alagappan 2005-04-01 12:46:32 UTC

Please fill in this template when reporting a bug, unless you know what you
are doing.
Description of Problem:


Steps to reproduce the problem:
1. EDS suddenly terminated when I was in a personal folder having more than
1000 contacts
2. Stoped Evolution. Started EDS in console and started Evolution.
3. Evolution focus on personal address book having 1000 contacts.
4. Selected another personal address book.

Actual Results:
EDS crashed

Expected Results:


How often does this happen? 
Tried once

Additional Information:
evolution-2.2.1.0.200503310400-0.snap.novell.0.1

Comment 1 Nagappan Alagappan 2005-04-01 12:46:48 UTC

Backtrace was generated from
'/opt/gnome/libexec/evolution-data-server-1.2'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 19505)]
[New Thread 32769 (LWP 19506)]
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 19505)]
[New Thread 32769 (LWP 19506)]
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 19505)]
[New Thread 32769 (LWP 19506)]
[New Thread 16386 (LWP 19507)]
[New Thread 98307 (LWP 19526)]
0x40a0a8bb in waitpid () from /lib/libc.so.6

+ Trace 57592

Thread 4 (Thread 98307 (LWP 19526))

#0 __pthread_sigsuspend
from /lib/libpthread.so.0
#1 __pthread_wait_for_restart_signal
from /lib/libpthread.so.0
#2 __pthread_alt_lock
from /lib/libpthread.so.0
#3 pthread_mutex_lock
from /lib/libpthread.so.0
#4 gnome_segv_handler
at server.c line 92
#5 __pthread_sighandler
from /lib/libpthread.so.0
#6 <signal handler called>
#7 e_book_backend_get_static_capabilities
at e-book-backend.c line 452
#8 impl_GNOME_Evolution_Addressbook_Book_getStaticCapabilities
at e-data-book.c line 196
#9 _ORBIT_skel_small_GNOME_Evolution_Addressbook_Book_getStaticCapabilities
at Evolution-DataServer-Addressbook-common.c line 304
#10 ORBit_POAObject_invoke
from /opt/gnome/lib/libORBit-2.so.0
#11 ORBit_OAObject_invoke
from /opt/gnome/lib/libORBit-2.so.0
#12 ORBit_small_invoke_adaptor
from /opt/gnome/lib/libORBit-2.so.0
#13 ORBit_POAObject_handle_request
from /opt/gnome/lib/libORBit-2.so.0
#14 ORBit_POAObject_invoke_incoming_request
from /opt/gnome/lib/libORBit-2.so.0
#15 giop_thread_queue_process
from /opt/gnome/lib/libORBit-2.so.0
#16 giop_request_handler_thread
from /opt/gnome/lib/libORBit-2.so.0
#17 g_thread_pool_thread_proxy
from /opt/gnome/lib/libglib-2.0.so.0
#18 g_thread_create_proxy
from /opt/gnome/lib/libglib-2.0.so.0
#19 pthread_start_thread
from /lib/libpthread.so.0
#20 clone
from /lib/libc.so.6

Comment 2 Sushma Rai 2005-08-27 09:19:31 UTC

Can you please try this now?

Comment 3 André Klapper 2005-09-28 12:08:22 UTC

retargetting from 1.3 to 1.5 to get rid of that busted milestones (as discussed
with harish on irc)

Comment 4 Devashish Sharma 2006-01-19 05:53:31 UTC

Not reproducible and stack trace also not useful.
Closing it for now, reopen if the issue reappears.