GNOME Bugzilla – Bug 452984
crash in Dia Diagram Editor: trying to save a diagram...
Last modified: 2007-09-16 19:01:18 UTC
Version: @0.96.1@ What were you doing when the application crashed? trying to save a diagram. Distribution: Debian lenny/sid Gnome Release: 2.19.4 2007-06-30 (GARNOME) BugBuddy Version: 2.18.1 System: Linux 2.6.21.5 #1 Thu Jun 28 00:07:28 MST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Enabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 60063744 vsize: 60063744 resident: 45293568 share: 16953344 rss: 45293568 rss_rlim: 4294967295 CPU usage: start_time: 1183348303 rtime: 400 utime: 359 stime: 41 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/home/boat/garnome/bin/dia' Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1227512128 (LWP 8167)] 0xb7f30410 in __kernel_vsyscall ()
+ Trace 145163
Thread 1 (Thread -1227512128 (LWP 8167))
----------- .xsession-errors --------------------- ** (process:1976): WARNING **: Credentials byte was not nul opening pop3 INBOX folder get dthanate@gmail.com pop://dthanate%40gmail.com@pop.gmail.com/ Find Items 0 GTK Accessibility Module initialized Bonobo accessibility support initialized ** CRITICAL **: menus_clear_recent: assertion `recent_merge_ids' failed aborting... GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized Cannot access memory at address 0x1 Cannot access memory at address 0x1 --------------------------------------------------
It was at the moment of crash in the middle of the "recent_merge_ids" assert in menus.c. It should just have returned nicely, though. Asking the author of the new menu code in bug #340352. Cannot reproduce by the description.
well.. in the function void menus_clear_recent (void); if I change the line >> g_return_if_fail (recent_merge_ids); to >> if (!recent_merge_ids) return; the problem disappears. This may be a problem in my glib installation though. :-/
There is no g_return_if_fail (recent_merge_ids); anymore. BTW: if you are using --g-fatal-warnings (or some some distributor does) it is normal that a g_warning leads to: ** CRITICAL **: menus_clear_recent: assertion `recent_merge_ids' failed aborting... I would not consider this a crash, though.