[GEDI] libgfapi possible memory leak

[Simon Turcotte-Langevin]

Yes, no problem.

-----Original Message-----
From: Poornima Gurusiddaiah [mailto:pgurusid at redhat.com] 
Sent: 28 avril 2017 00:38
To: Raghavendra Gowdappa <rgowdapp at redhat.com>
Cc: Simon Turcotte-Langevin <simon.turcotte-langevin at ubisoft.com>; Pranith Kumar Karampuri <pkarampu at redhat.com>; ndevos at redhat.com; Ravishankar N <ravishankar at redhat.com>; Kotresh Hiremath Ravishankar <khiremat at redhat.com>; Soumya Koduri <skoduri at redhat.com>
Subject: Re: libgfapi possible memory leak

Can you attach the gfapi sample program sent in the original mail?

Thanks,
Poornima

----- Original Message -----
> From: "Raghavendra Gowdappa" <rgowdapp at redhat.com>
> To: "Simon Turcotte-Langevin" <simon.turcotte-langevin at ubisoft.com>
> Cc: "Pranith Kumar Karampuri" <pkarampu at redhat.com>, 
> ndevos at redhat.com, "Ravishankar N" <ravishankar at redhat.com>, "Kotresh Hiremath Ravishankar" <khiremat at redhat.com>, "Soumya Koduri" <skoduri at redhat.com>, "Poornima Gurusiddaiah"
> <pgurusid at redhat.com>
> Sent: Friday, April 28, 2017 10:00:44 AM
> Subject: Re: libgfapi possible memory leak
> 
> +Soumya, +Poornima
> 
> ----- Original Message -----
> > From: "Simon Turcotte-Langevin" 
> > <simon.turcotte-langevin at ubisoft.com>
> > To: "Raghavendra Gowdappa" <rgowdapp at redhat.com>, "Pranith Kumar Karampuri"
> > <pkarampu at redhat.com>, ndevos at redhat.com, "Ravishankar N" 
> > <ravishankar at redhat.com>, "Kotresh Hiremath Ravishankar"
> > <khiremat at redhat.com>
> > Sent: Friday, April 28, 2017 12:30:38 AM
> > Subject: libgfapi possible memory leak
> > 
> > Hello everyone,
> > 
> > We have a memory leak issue with our client implementation, and 
> > we're trying to track it down. I've built a sample program that 
> > mounts a gluster virtual mount, opens a file descriptor, read from 
> > it, then closes the file descriptor then finally unmounts the 
> > virtual mount.
> > 
> > Valgrind reports many memory leaks, and I'd like to know if those 
> > are false positives reported by valgrind, caused by a custom memory 
> > and resource management, or if those are indeed memory leaks in 
> > libgfapi. It might be that the code sample I attached does not close 
> > all resources. If that's the case, could you tell us what are the 
> > methods we should call to release all resources?
> > 
> > Commands:
> > gcc -o libgfapi-memleak -lgfapi libgfapi-memleak.c valgrind 
> > --leak-check=full --log-file="valgrind.out" memleak-libgfapi
> > 
> > Thanks!
> > 
> > 
> > [cid:image003.png at 01D2BF67.0834CB20]
> > 
> > Simon Turcotte-Langevin
> > Tool Programmer - Asset Store<http://magneto/> Technology Group - 
> > Ubisoft Montreal
> > 
> > 
> > 
> > 
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: memleak-libgfapi.zip
Type: application/x-zip-compressed
Size: 8352 bytes
Desc: memleak-libgfapi.zip
URL: <http://lists.gluster.org/pipermail/integration/attachments/20170428/fdf68f15/attachment.bin>