GNOME Bugzilla – Bug 266960
Intermittent crash when waiting for auto-complete from ldap server
Last modified: 2005-09-28 12:32:10 UTC
Distribution: Debian 3.1 Package: Evolution-Data-Server Priority: Normal Version: 1.0.0 Synopsis: Intermittent crash when waiting for auto-complete from ldap server Bugzilla-Product: Evolution-Data-Server Bugzilla-Component: Contacts Bugzilla-Version: 1.0.0 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: I just typed in a contact name in the To: field, waited a second or so and the dialogue for the data-server crash came up. It occasionally has a problem where it grabs 100% of the cpu until I kill it, but this time it just crashed. Steps to reproduce the crash: 1. Type in a name 2. wait 1 sec .. Expected Results: The same record returned that works at other times How often does this happen? Intermittently Additional Information: Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Backtrace would help. Otherwise this is too vague to pinpoint the problem... Please reopen this report when you add a backtrace.
Hi, Backtrace got after attempting auto-complete on a surname, then backspacing and issuing a different name while the search is still in progress. Repeated twice and I got the folloeing : [New Thread -1308558416 (LWP 4554)] looked up msgid 54, got op 0x81b8f30 ldap_search_handler (0xb4404038) stop_book_view (0xb4404038) ldap_search_dtor (0xb4404038) start_book_view (0x81bff68) searching server using filter: (| (|(fileAs=smith*)(&(!(fileAs=*))(sn=smith*))) (|(cn=smith*)(sn=smith*)) (mail=smith*) (displayName=smith*) ) (expecting max 100 results) adding search_op (0x81bff68, 56) Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1291781200 (LWP 4549)] 0x081b1668 in ?? () (gdb) thread apply all bt
+ Trace 50745
Thread 177 (Thread -1308558416 (LWP 4554))
Thread 176 (Thread -1226634320 (LWP 4553))
Poornima, Do you get evolution-qa@novel.com mails. If not, you and Ramesh Babu needs to get into the list.
This looks like a dupe of 68630.
You mean 68360, right?
Yes. *** This bug has been marked as a duplicate of 268360 ***
Removed erroneous target milestone values and set them to FUTURE