[maemo-developers] delete-event processing of GtkWindow causes cordump

From: Zhu, Peter J peter.j.zhu at intel.com
Date: Mon Jul 23 11:36:49 EEST 2007
Hi,

As I wrote one application for new hildon-1/hildon-wm, I found there is
a serious problem
with one of the toplevel windows it creates. If one tries to close that
window by click X at top right corner, coredump happens. Then
I tried to found the difference of that window with others. Then
I found that the buggy window has connected with "delete-event" signal
and the callback of the signal returns FALSE to let window continue
destroy. 

To verify the issue is NOT caused by the special application logic
itself, I write one very simle program that only creates one toplevel
window and has delete-event-cb callback. If the callback returns TRUE,
no problem. If it returns FALSE, then the program coredump as attched at
last of mail.

In my understanding it should be a problem of components of app
framework. It might be hildon-wm, matchbox or gtk porting
itself. 

Your thoughts? -Peter

*** glibc detected *** /opt/hildon-hello: free(): invalid next size
(fast): 0x080bf3a0 ***
======= Backtrace: =========
/lib/libc.so.6[0xb76f6ef2]
/lib/libc.so.6(cfree+0x89)[0xb76f8bb9]
/usr/lib/libglib-2.0.so.0(g_free+0x31)[0xb77fb8e1]
/usr/lib/libhildon-1.so.0[0xb7fbc60f]
/usr/lib/libgobject-2.0.so.0(g_object_unref+0x16c)[0xb7893a9c]
/usr/lib/libgtk-x11-2.0.so.0(gtk_main_do_event+0x196)[0xb7d307e6]
/usr/lib/libgdk-x11-2.0.so.0[0xb7b85c3a]
/usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x17c)[0xb77f410c]
/usr/lib/libglib-2.0.so.0[0xb77f754f]
/usr/lib/libglib-2.0.so.0(g_main_loop_run+0x1a9)[0xb77f78f9]
/usr/lib/libgtk-x11-2.0.so.0(gtk_main+0xb4)[0xb7d30ea4]
/opt/hildon-hello[0x8048ae9]
/lib/libc.so.6(__libc_start_main+0xe0)[0xb76a7030]
/opt/hildon-hello[0x8048941]

More information about the maemo-developers mailing list