GNOME Bugzilla – Bug 323753
Address List Rapid Mouse Click Crash
Last modified: 2006-01-26 17:36:45 UTC
Distribution: Unknown Package: Evolution Severity: Normal Version: GNOME2.12.2 unspecified Gnome-Distributor: FreeBSD GNOME Project Synopsis: Adress List Rapid Mouse Click Crash Bugzilla-Product: Evolution Bugzilla-Component: Contacts [was: Addressbook] Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.12.0) Description: Description of the crash: Composing an email, hit To: opens address book, click your contact with rapid mouse clicks and evolution core dumps. To see it work do this keep clicking a contacts name ina frenzy and it will core dump real soon. Steps to reproduce the crash: 1. compose Mail 2. Hit To: field to pop upon address book 3. Click a contact rapidly and repeatedly Expected Results: Should not crash How often does this happen? Always Additional Information: Debugging Information: Backtrace was generated from '/usr/X11R6/bin/evolution-2.4' (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[New Thread 0x8531000 (runnable)] [New Thread 0x85aaa00 (runnable)] [New Thread 0x82e7c00 (sleeping)] [New Thread 0x84c4a00 (sleeping)] [New Thread 0x8454e00 (sleeping)] [New Thread 0x81ee400 (sleeping)] [New Thread 0x818a400 (sleeping)] [New Thread 0x818a200 (LWP 100239)] [New Thread 0x806b000 (runnable)] [New LWP 100270] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Switching to LWP 100270] 0x28fce277 in pthread_testcancel () from /usr/lib/libpthread.so.2
+ Trace 64528
Thread 10 (LWP 100270)
------- Bug moved to this database by unknown@gnome.bugs 2005-12-10 21:09 UTC -------
Can confirm this.
Does this always happen? The stack traces above are not useful. I tried the same and got the, the different trace. (gdb) bt
+ Trace 64554
From the traces, it does not look like evolution bug.
For same steps stack trace on my system
+ Trace 64555
Yes it always happens it either freezes or core dumps. The gdb posted orginally was auto attached via bug buddy. The problem here is getting a good backtrace. I tired a couple of times -- sometimes it would freeze and not provide function names so pretty much being useless. Again this doesnt help the evo trace. It should be noted other gnome apps do not respond this way to mouse clicks. Manual gdb backtrace (gdb) bt
+ Trace 64558
Removed OS=FreeBSD, can confirm this on Linux.
*** Bug 323514 has been marked as a duplicate of this bug. ***
Marking as duplicate of bug 328712, which got the best stacktrace so far. Thanks for taking the time to report this issue! Feel free to report any further issue you find. *** This bug has been marked as a duplicate of 328712 ***