GNOME Bugzilla – Bug 395272
Opening preview pane sometimes causes app crash
Last modified: 2012-02-15 13:09:15 UTC
What were you doing when the application crashed? Changed folders (from Inbox to a vFolder), selected an unread message (POP), and opened the preview pane. Crash. Distribution: Gentoo Base System version 1.12.6 Gnome Release: 2.16.1 2006-11-06 (Gentoo) BugBuddy Version: 2.16.0 Memory status: size: 197251072 vsize: 0 resident: 197251072 share: 0 rss: 59150336 rss_rlim: 0 CPU usage: start_time: 1168478898 rtime: 0 utime: 11015 stime: 0 cutime:9774 cstime: 0 timeout: 1241 it_real_value: 0 frequency: 2018 Backtrace was generated from '/usr/bin/evolution-2.8' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1229306192 (LWP 9429)] [New Thread -1288995936 (LWP 13854)] [New Thread -1299190880 (LWP 13851)] [New Thread -1290798176 (LWP 9456)] [New Thread -1280316512 (LWP 9451)] [New Thread -1261605984 (LWP 9443)] [New Thread -1252680800 (LWP 9442)] [New Thread -1244251232 (LWP 9439)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 101163
Thread 1 (Thread -1229306192 (LWP 9429))
Hey, Bug Buddy works now. Cool. If I need to do something to provide _more_ thread trace data, please say so. I've noticed this a few times, and it seems to be when preview pane is opened. AfC
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Waiting on a build from my distro for Evolution 2.8.3; I will report back with a new stack trace then. AfC
Still occuring with 2.8.3. Working on getting a stack trace. AfC
andrew, is this still an issue?
In 2.8.3, yes. I only jusy upgraded to GNOME 2.18 and am so compulsively out of the habit of ever opening the preview pane it was so crashy that I have to get back into the groove of using it again. So it's too early to tell if it's been fixed. AfC
*** Bug 451877 has been marked as a duplicate of this bug. ***
*** Bug 453127 has been marked as a duplicate of this bug. ***
*** Bug 405777 has been marked as a duplicate of this bug. ***
(In reply to comment #1) > Hey, Bug Buddy works now. Cool. If I need to do something to provide _more_ > thread trace data, please say so. Hey Andrew, of course you can. ;-) According to the stacktraces so far, we would need a stacktrace with debugging symbols for the usual suspects [1], plus debugginf symbols for gconf in this case. gconf symbols are missing from all duplicates. [1] debugging packages for evolution, evolution-data-server and gtkhtml, plus debugging packages for glib, gtk+ and gnome-vfs, GNOME's main libraries
I believe this to be the same issue as bug 405777 and its duplicates. The small difference in the stacktrace most likely is due to debugging symbols. Pasting that stacktrace below for better search support. Also, this crash seems to still be valid in 2.10.x.
+ Trace 145321
REOPENing and CONFIRMing as per duplicates and the pretty good stacktrace. (Inheriting a bunch of Cc's.) However, a new stacktrace with debugging symbols for gconf still would be great. Can anyone of you guys provide us with one?
*** Bug 460669 has been marked as a duplicate of this bug. ***
Created attachment 93831 [details] [review] Code Cleanups
GPOINTER_TO_INT (NULL) will not crash. so the gpointer check in the above patch may not be of much use. The other cleanups are needed I guess.
The function return type is void... + g_return_val_if_fail (esb != NULL, NULL); + g_return_val_if_fail (E_IS_SEARCH_BAR (esb), NULL);
*** Bug 474025 has been marked as a duplicate of this bug. ***
*** Bug 486934 has been marked as a duplicate of this bug. ***
Created attachment 97681 [details] [review] code cleanup just using g_return_if_fail() instead of g_return_val_if_fail() But the main issue won't be fixed with this patch
Tobias, looks fine to commit.
*** Bug 489814 has been marked as a duplicate of this bug. ***
committed as rev 34437. lowering severity and priority according to comment #18
*** Bug 495004 has been marked as a duplicate of this bug. ***
Shall we close the bug ? This bug hasn't got any duplicates for almost one and half year.
(In reply to comment #23) > Shall we close the bug ? > This bug hasn't got any duplicates for almost one and half year. Closing. Please reopen if this is still an issue in a recent version.