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 627615 - event_page memory leak
event_page memory leak
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Calendar
2.32.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks: 627707
 
 
Reported: 2010-08-21 23:59 UTC by David Woodhouse
Modified: 2015-04-21 16:24 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description David Woodhouse 2010-08-21 23:59:13 UTC
==30229== 36 bytes in 3 blocks are definitely lost in loss record 10,452 of 25,767
==30229==    at 0x4A0515D: malloc (vg_replace_malloc.c:195)
==30229==    by 0x3A4DC45784: g_malloc (in /lib64/libglib-2.0.so.0.2512.0)
==30229==    by 0x3A4DC5D2DD: g_strdup (in /lib64/libglib-2.0.so.0.2512.0)
==30229==    by 0x34FA88B288: ??? (in /usr/lib64/libgtk-x11-2.0.so.0.2000.1)
==30229==    by 0x3A4DC430F1: ??? (in /lib64/libglib-2.0.so.0.2512.0)
==30229==    by 0x3A4DC44B28: g_markup_parse_context_parse (in /lib64/libglib-2.0.so.0.2512.0)
==30229==    by 0x34FA88A571: ??? (in /usr/lib64/libgtk-x11-2.0.so.0.2000.1)
==30229==    by 0x34FA889E5E: gtk_builder_add_from_file (in /usr/lib64/libgtk-x11-2.0.so.0.2000.1)
==30229==    by 0x6B59C68: e_load_ui_builder_definition (e-util.c:307)
==30229==    by 0xEC9B2D9: event_page_construct (event-page.c:3153)
==30229==    by 0xEC9E15C: event_page_new (event-page.c:3215)
==30229==    by 0xEC99C1D: event_editor_constructor (event-editor.c:316)
Comment 1 Matthew Barnes 2010-08-27 14:14:31 UTC
This looks like it might be a leak in GLib or GTK+.  If you're still capturing valgrind logs, can you install debugging symbols for these packages and post another trace so I can get a better look?
Comment 2 David Woodhouse 2010-09-08 15:47:14 UTC
This looks very similar but does the presence of debuginfo account for the fact that it's managed to find two extra stack frames between g_markup_parse_context_parse() and g_strdup() ? 

Note also that this one is 'possibly lost', which I've been ignoring so far although I suspect a lot of them are real leaks too.

==21464== 28 bytes in 4 blocks are possibly lost in loss record 13,009 of 45,053
==21464==    at 0x4A0615D: malloc (vg_replace_malloc.c:195)
==21464==    by 0x3D3D645C80: g_malloc (gmem.c:134)
==21464==    by 0x3D3D65E31D: g_strdup (gstrfuncs.c:101)
==21464==    by 0x3D3EE87597: gtk_buildable_set_name (gtkbuildable.c:67)
==21464==    by 0x3D3EE8944A: _gtk_builder_construct (gtkbuilder.c:498)
==21464==    by 0x3D3EE8BEDC: start_element (gtkbuilderparser.c:787)
==21464==    by 0x3D3D642689: emit_start_element (gmarkup.c:922)
==21464==    by 0x3D3D6440D8: g_markup_parse_context_parse (gmarkup.c:1260)
==21464==    by 0x3D3EE8A571: _gtk_builder_parser_parse_buffer (gtkbuilderparser.c:1162)
==21464==    by 0x3D3EE89E5E: gtk_builder_add_from_file (gtkbuilder.c:678)
==21464==    by 0x5E45FB8: e_load_ui_builder_definition (e-util.c:307)
==21464==    by 0xEC9EFC9: event_page_construct (event-page.c:3153)
Comment 3 Milan Crha 2015-04-21 16:24:12 UTC
I do not see this with current git master, which is pretty much the same as 3.16.1, thus I'm closing this.