After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 403148 - leaks reported by valgrind
leaks reported by valgrind
Status: RESOLVED OBSOLETE
Product: metacity
Classification: Other
Component: general
trunk
Other Linux
: Normal normal
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
: 475473 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-02-01 10:10 UTC by Kjartan Maraas
Modified: 2016-07-15 12:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Kjartan Maraas 2007-02-01 10:10:25 UTC
Valgrind reports the following leaks:

==3919== 548 (120 direct, 428 indirect) bytes in 14 blocks are definitely lost in loss record 99 of 200
==3919==    at 0x40053C0: malloc (vg_replace_malloc.c:149)
==3919==    by 0x4693545: g_malloc (gmem.c:131)
==3919==    by 0x46A2FC7: g_slice_alloc (gslice.c:777)
==3919==    by 0x46A4111: g_slist_prepend (gslist.c:91)
==3919==    by 0x805FBA1: meta_display_compute_resistance_and_snapping_edges (edge-resistance.c:967)
==3919==    by 0x8059957: meta_display_begin_grab_op (display.c:3485)
==3919==    by 0x80563EA: meta_core_begin_grab_op (core.c:649)
==3919==    by 0x8064893: meta_frames_button_press_event (frames.c:1462)
==3919==    by 0x4137D2F: _gtk_marshal_BOOLEAN__BOXED (gtkmarshalers.c:84)
==3919==    by 0x462F4F8: g_type_class_meta_marshal (gclosure.c:567)
==3919==    by 0x4630D0A: g_closure_invoke (gclosure.c:490)
==3919==    by 0x4641DA2: signal_emit_unlocked_R (gsignal.c:2478)
==3919==    by 0x4642A3E: g_signal_emit_valist (gsignal.c:2209)
==3919==    by 0x4642E38: g_signal_emit (gsignal.c:2243)
==3919==    by 0x424BBC7: gtk_widget_event_internal (gtkwidget.c:3915)
==3919==    by 0x4131102: gtk_propagate_event (gtkmain.c:2335)
==3919==    by 0x4132306: gtk_main_do_event (gtkmain.c:1569)
==3919==    by 0x4387879: gdk_event_dispatch (gdkevents-x11.c:2318)
==3919==    by 0x468C0C1: g_main_context_dispatch (gmain.c:2045)
==3919==    by 0x468F08E: g_main_context_iterate (gmain.c:2677)
==3919==    by 0x468F438: g_main_loop_run (gmain.c:2881)
==3919==    by 0x806D890: main (main.c:391)

and

==3919== 381 bytes in 24 blocks are definitely lost in loss record 125 of 200
==3919==    at 0x40053C0: malloc (vg_replace_malloc.c:149)
==3919==    by 0x46F7AFA: sn_malloc (sn-util.c:102)
==3919==    by 0x46F7B60: sn_internal_strndup (sn-util.c:273)
==3919==    by 0x46F7CB1: parse_prefix_up_to (sn-xmessages.c:580)
==3919==    by 0x46F7E1D: sn_internal_unserialize_message (sn-xmessages.c:676)
==3919==    by 0x46F6D48: xmessage_func (sn-monitor.c:694)
==3919==    by 0x46F816D: dispatch_message_foreach (sn-xmessages.c:400)
==3919==    by 0x46F634A: sn_list_foreach (sn-list.c:157)
==3919==    by 0x46F8369: sn_internal_xmessage_process_event (sn-xmessages.c:452)
==3919==    by 0x46F54DA: sn_display_process_event (sn-common.c:180)
==3919==    by 0x805AE91: event_callback (display.c:1471)
==3919==    by 0x80922AF: filter_func (ui.c:88)
==3919==    by 0x43841E0: gdk_event_apply_filters (gdkevents-x11.c:343)
==3919==    by 0x4385890: gdk_event_translate (gdkevents-x11.c:892)
==3919==    by 0x4387486: _gdk_events_queue (gdkevents-x11.c:2252)
==3919==    by 0x438784E: gdk_event_dispatch (gdkevents-x11.c:2312)
==3919==    by 0x468C0C1: g_main_context_dispatch (gmain.c:2045)
==3919==    by 0x468F08E: g_main_context_iterate (gmain.c:2677)
==3919==    by 0x468F438: g_main_loop_run (gmain.c:2881)
==3919==    by 0x806D890: main (main.c:391)
Comment 1 Kjartan Maraas 2007-02-01 13:42:19 UTC
There's a chance the last one of these two is fixed in SN CVS already, but we need someone to do a 0.9 release of that...
Comment 2 Thomas Thurman 2007-12-11 15:32:24 UTC
*** Bug 475473 has been marked as a duplicate of this bug. ***
Comment 3 Thomas Thurman 2007-12-11 15:38:22 UTC
*** Bug 475473 has been marked as a duplicate of this bug. ***
Comment 4 Thomas Thurman 2007-12-11 15:39:03 UTC
Comment from bug 475473:

Valgrind reports the following leaks:

==3919== 548 (120 direct, 428 indirect) bytes in 14 blocks are definitely lost
in loss record 99 of 200
==3919==    at 0x40053C0: malloc (vg_replace_malloc.c:149)
==3919==    by 0x4693545: g_malloc (gmem.c:131)
==3919==    by 0x46A2FC7: g_slice_alloc (gslice.c:777)
==3919==    by 0x46A4111: g_slist_prepend (gslist.c:91)
==3919==    by 0x805FBA1: meta_display_compute_resistance_and_snapping_edges
(edge-resistance.c:967)
==3919==    by 0x8059957: meta_display_begin_grab_op (display.c:3485)
==3919==    by 0x80563EA: meta_core_begin_grab_op (core.c:649)
==3919==    by 0x8064893: meta_frames_button_press_event (frames.c:1462)
==3919==    by 0x4137D2F: _gtk_marshal_BOOLEAN__BOXED (gtkmarshalers.c:84)
==3919==    by 0x462F4F8: g_type_class_meta_marshal (gclosure.c:567)
==3919==    by 0x4630D0A: g_closure_invoke (gclosure.c:490)
==3919==    by 0x4641DA2: signal_emit_unlocked_R (gsignal.c:2478)
==3919==    by 0x4642A3E: g_signal_emit_valist (gsignal.c:2209)
==3919==    by 0x4642E38: g_signal_emit (gsignal.c:2243)
==3919==    by 0x424BBC7: gtk_widget_event_internal (gtkwidget.c:3915)
==3919==    by 0x4131102: gtk_propagate_event (gtkmain.c:2335)
==3919==    by 0x4132306: gtk_main_do_event (gtkmain.c:1569)
==3919==    by 0x4387879: gdk_event_dispatch (gdkevents-x11.c:2318)
==3919==    by 0x468C0C1: g_main_context_dispatch (gmain.c:2045)
==3919==    by 0x468F08E: g_main_context_iterate (gmain.c:2677)
==3919==    by 0x468F438: g_main_loop_run (gmain.c:2881)
==3919==    by 0x806D890: main (main.c:391)

and

==3919== 381 bytes in 24 blocks are definitely lost in loss record 125 of 200
==3919==    at 0x40053C0: malloc (vg_replace_malloc.c:149)
==3919==    by 0x46F7AFA: sn_malloc (sn-util.c:102)
==3919==    by 0x46F7B60: sn_internal_strndup (sn-util.c:273)
==3919==    by 0x46F7CB1: parse_prefix_up_to (sn-xmessages.c:580)
==3919==    by 0x46F7E1D: sn_internal_unserialize_message (sn-xmessages.c:676)
==3919==    by 0x46F6D48: xmessage_func (sn-monitor.c:694)
==3919==    by 0x46F816D: dispatch_message_foreach (sn-xmessages.c:400)
==3919==    by 0x46F634A: sn_list_foreach (sn-list.c:157)
==3919==    by 0x46F8369: sn_internal_xmessage_process_event
(sn-xmessages.c:452)
==3919==    by 0x46F54DA: sn_display_process_event (sn-common.c:180)
==3919==    by 0x805AE91: event_callback (display.c:1471)
==3919==    by 0x80922AF: filter_func (ui.c:88)
==3919==    by 0x43841E0: gdk_event_apply_filters (gdkevents-x11.c:343)
==3919==    by 0x4385890: gdk_event_translate (gdkevents-x11.c:892)
==3919==    by 0x4387486: _gdk_events_queue (gdkevents-x11.c:2252)
==3919==    by 0x438784E: gdk_event_dispatch (gdkevents-x11.c:2312)
==3919==    by 0x468C0C1: g_main_context_dispatch (gmain.c:2045)
==3919==    by 0x468F08E: g_main_context_iterate (gmain.c:2677)
==3919==    by 0x468F438: g_main_loop_run (gmain.c:2881)
==3919==    by 0x806D890: main (main.c:391)
Comment 5 Elijah Newren 2007-12-12 04:58:21 UTC
Thomas: Did you accidentally cut-n-paste from this bug report into this bug report, instead of from bug 475473?  ;-)
Comment 6 Thomas Thurman 2007-12-12 12:50:15 UTC
Yes. Sigh.

==2727== 472 (52 direct, 420 indirect) bytes in 7 blocks are definitely lost in
loss record 95 of 187
==2727==    at 0x4022525: malloc (vg_replace_malloc.c:149)
==2727==    by 0x47E24D5: g_malloc (gmem.c:131)
==2727==    by 0x47F6D2A: g_slice_alloc (gslice.c:824)
==2727==    by 0x47F7F61: g_slist_prepend (gslist.c:91)
==2727==    by 0x80586CA: listify_func (display.c:814)
==2727==    by 0x47CDAB5: g_hash_table_foreach (ghash.c:680)
==2727==    by 0x805A70E: meta_display_list_windows (display.c:836)
==2727==    by 0x805602D: meta_invalidate_default_icons (core.c:728)
==2727==    by 0x806E194: prefs_changed_callback (main.c:468)
==2727==    by 0x8073C7E: changed_idle_handler (prefs.c:250)
==2727==    by 0x47D8FA0: g_idle_dispatch (gmain.c:4132)
==2727==    by 0x47DAB6B: g_main_context_dispatch (gmain.c:2061)
==2727==    by 0x47DDF9E: g_main_context_iterate (gmain.c:2694)
==2727==    by 0x47DE348: g_main_loop_run (gmain.c:2898)
==2727==    by 0x806DDE5: main (main.c:392)
==2727==
==2727==
==2727== 720 bytes in 58 blocks are definitely lost in loss record 131 of 187
==2727==    at 0x4021864: calloc (vg_replace_malloc.c:279)
==2727==    by 0x47E243D: g_malloc0 (gmem.c:150)
==2727==    by 0x8080C5B: meta_color_spec_new (theme.c:986)
==2727==    by 0x808345B: meta_color_spec_new_from_string (theme.c:1096)
==2727==    by 0x80839A9: meta_color_spec_new_from_string (theme.c:1149)
==2727==    by 0x808987D: parse_color (theme-parser.c:725)
==2727==    by 0x808C0D0: start_element_handler (theme-parser.c:1907)
==2727==    by 0x47E0DC0: g_markup_parse_context_parse (gmarkup.c:1328)
==2727==    by 0x8090CE2: meta_theme_load (theme-parser.c:4595)
==2727==    by 0x8085E6A: meta_theme_set_current (theme.c:4489)
==2727==    by 0x8091937: meta_ui_set_current_theme (ui.c:718)
==2727==    by 0x806E194: prefs_changed_callback (main.c:468)
==2727==    by 0x8073C7E: changed_idle_handler (prefs.c:250)
==2727==    by 0x47D8FA0: g_idle_dispatch (gmain.c:4132)
==2727==    by 0x47DAB6B: g_main_context_dispatch (gmain.c:2061)
==2727==    by 0x47DDF9E: g_main_context_iterate (gmain.c:2694)
==2727==    by 0x47DE348: g_main_loop_run (gmain.c:2898)
==2727==    by 0x806DDE5: main (main.c:392)
Comment 7 Kjartan Maraas 2016-07-15 12:20:27 UTC
Closing as obsolete.