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 313845 - Leak in gam_server
Leak in gam_server
Status: RESOLVED FIXED
Product: gamin
Classification: Other
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Gamin Maintainer(s)
Gamin Maintainer(s)
Depends on:
Blocks: 313846
 
 
Reported: 2005-08-18 15:04 UTC by Kjartan Maraas
Modified: 2005-09-08 10:24 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Kjartan Maraas 2005-08-18 15:04:15 UTC 
Valgrind found this in 0.1.5:

==2623== 7311 (3680 direct, 3631 indirect) bytes in 115 blocks are definitely
lost in loss record 108 of 110
==2623==    at 0x1B904B64: calloc (vg_replace_malloc.c:279)
==2623==    by 0x1B930BFB: g_malloc0 (gmem.c:154)
==2623==    by 0x804A768: ??? (gam_subscription.c:74)
==2623==    by 0x80501D3: ??? (gam_connection.c:358)
==2623==    by 0x804F538: ??? (gam_channel.c:283)
==2623==    by 0x1B9506E2: g_io_unix_dispatch (giounix.c:162)
==2623==    by 0x1B92A6FD: g_main_context_dispatch (gmain.c:1934)
==2623==    by 0x1B92D4CD: g_main_context_iterate (gmain.c:2565)
==2623==    by 0x1B92D9CE: g_main_loop_run (gmain.c:2769)
==2623==    by 0x804B69C: ??? (gam_server.c:424)
==2623==    by 0x1B9B849E: __libc_start_main (in /lib/libc-2.3.90.so)
==2623==    by 0x804A6B0: (within /usr/libexec/gam_server)
Comment 1 John McCutchan 2005-08-18 18:15:17 UTC 
I'm pretty sure this is harmless. When gam_server shutsdown it doesn't clean up
after itself. This isn't a leak, it's just gamin not playing nice with valgrind.
Comment 2 Daniel Veillard 2005-09-08 10:24:00 UTC 
I found out that when running with inotify, the subscriptions blocks are
*never* freed ! This is not a valgrind problem, this is not harmless, this
was a serious bug. 
  Fixed in CVS !

Daniel