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 693718 - Memory leak, maybe in glib-networking?
Memory leak, maybe in glib-networking?
Status: RESOLVED FIXED
Product: libsoup
Classification: Core
Component: Misc
2.40.x
Other Linux
: Normal normal
: ---
Assigned To: libsoup-maint@gnome.bugs
libsoup-maint@gnome.bugs
Depends on:
Blocks:
 
 
Reported: 2013-02-13 15:43 UTC by Milan Crha
Modified: 2013-02-13 16:14 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Milan Crha 2013-02-13 15:43:44 UTC 
I see thie below memory leak quite few times in a valgrind log. I'm pretty sure the SoupMessage is properly freed, thus I guess it's somewhere else. Please check it out. Thanks.

  80 bytes in 2 blocks are definitely lost in loss record 7,315 of 10,977
     at 0x4A0883C: malloc (vg_replace_malloc.c:270)
     by 0x3D01E84A9E: g_mutex_impl_new (gthread-posix.c:88)
     by 0x3D01E84B5C: g_mutex_get_impl (gthread-posix.c:125)
     by 0x3D01E84D98: g_mutex_lock (gthread-posix.c:210)
     by 0x243AB8DF: ??? (in /usr/lib64/gio/modules/libgiognutls.so)
     by 0x243AB502: ??? (in /usr/lib64/gio/modules/libgiognutls.so)
     by 0x243AC24F: ??? (in /usr/lib64/gio/modules/libgiognutls.so)
     by 0x33E5A73ADC: soup_socket_handshake_sync (soup-socket.c:1125)
     by 0x33E5A4EEA8: soup_connection_connect_sync (soup-connection.c:658)
     by 0x33E5A712D4: process_queue_item (soup-session-sync.c:175)
     by 0x33E5A71554: soup_session_sync_send_message (soup-session-sync.c:335)
     by 0x18A0655E: send_and_handle_redirection (e-cal-backend-caldav.c:1064)
Comment 1 Dan Winship 2013-02-13 16:14:42 UTC 
yup. thanks