Hi, $)C@LA&Hq <[EMAIL PROTECTED]> writes:
> I compiled dfb 0.9.11 using --enable-debug. And then I ran > > example "df_window"... > > But I don't know why df_window generated following memory leak messages.. > > .... > (-) [348: 16639] chunk 0x101dbdf0 allocated in tree_node_new (tree.c: > 122) not free'd !! > (-) [348: 16971] chunk 0x101cce28 allocated in dfb_font_get_glyph_data > (fonts.c: 93) not free'd !! > (-) [348: 16971] chunk 0x101dbb78 allocated in tree_node_new (tree.c: > 122) not free'd !! > (-) [348: 16972] chunk 0x100529e0 allocated in IDirectFBWindow_Construct > (idirectfbwindow.c: 673) not free'd !! > (-) [348: 16972] chunk 0x101cc158 allocated in IDirectFBWindow_React > (idirectfbwindow.c: 732) not free'd !! > (-) [348: 16972] chunk 0x101d0420 allocated in > IDirectFBSurface_Window_Construct (idirectfbsurface_window.c: 220) not free > ..... these are resources the application allocated through DirectFB and didn't release before it quit. Of course the OS will take care of cleaning up after the application or, in the case that the application was using the multi-application core, DirectFB does this job. In this special case it looks as if df_window forgot to release one of it's windows. The window surface had a reference on a font and thus that font wasn't released as well. > Any way to remove those memory leak messages? yes, update DirectFB and DirectFB-examples. With the current df_window implementation you'll get other leaks ;-) Salut, Sven -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe directfb-users" as subject.
