GNOME Bugzilla – Bug 156810
Memory leak for icons
Last modified: 2005-04-29 18:12:43 UTC
I'm seeing leak for icons. This case is for a Save-as from gnumeric. Naively it looks like both icon_info_ensure_scale_and_pixbuf and its caller, gtk_icon_info_load_icon. ref the pixbuf. MLK: 1296 bytes leaked at 0x1728ab8 This memory was allocated from: malloc [rtlib.o pc=0x72e00] g_try_malloc [gmem.c:194 pc=0xfa3c5cac] gdk_pixbuf_new [gdk-pixbuf.c:281 pc=0xfb304d78] gdk_pixbuf_scale_simple [gdk-pixbuf-scale.c:252 pc=0xfb30e8c8] icon_info_ensure_scale_and_pixbuf [gtkicontheme.c:2531 pc=0xfad90f38] gtk_icon_info_load_icon [gtkicontheme.c:2571 pc=0xfad91008] gtk_icon_theme_load_icon [gtkicontheme.c:1312 pc=0xfad8e100] get_cached_icon [gtkfilesystemgnomevfs.c:948 pc=0xf7ab4bcc] gtk_file_system_gnome_vfs_render_icon [gtkfilesystemgnomevfs.c:1405 pc=0xf7ab58fc] gtk_file_system_render_icon [gtkfilesystem.c:697 pc=0xfad62640] shortcuts_reload_icons [gtkfilechooserdefault.c:984 pc=0xfad49024] change_icon_theme [gtkfilechooserdefault.c:3903 pc=0xfad4fe50] check_icon_theme [gtkfilechooserdefault.c:3939 pc=0xfad4fffc] gtk_file_chooser_default_screen_changed [gtkfilechooserdefault.c:3972 pc=0xfad501d4] g_cclosure_marshal_VOID__OBJECT [gmarshal.c:636 pc=0xfa868270] g_type_class_meta_marshal [gclosure.c:514 pc=0xfa83e10c] g_closure_invoke [gclosure.c:437 pc=0xfa83dd4c] signal_emit_unlocked_R [gsignal.c:2480 pc=0xfa865f80] g_signal_emit_valist [gsignal.c:2201 pc=0xfa862b74] g_signal_emit [gsignal.c:2245 pc=0xfa862fd4] do_screen_change [gtkwidget.c:4789 pc=0xfaf95f94] gtk_widget_propagate_hierarchy_changed_recurse [gtkwidget.c:4813 pc=0xfaf96150] gtk_box_forall [gtkbox.c:702 pc=0xfac8eab8] gtk_container_forall [gtkcontainer.c:1265 pc=0xfacf7654] gtk_widget_propagate_hierarchy_changed_recurse [gtkwidget.c:4816 pc=0xfaf961d0] _gtk_widget_propagate_hierarchy_changed [gtkwidget.c:4853 pc=0xfaf96320] gtk_widget_set_parent [gtkwidget.c:4314 pc=0xfaf94920] gtk_box_pack_start [gtkbox.c:389 pc=0xfac8d968] gtk_file_chooser_dialog_constructor [gtkfilechooserdialog.c:393 pc=0xfad4488c]
Does this still happen? The code has changed a lot...
Seems gone.