[Gluster-users] Gfapi memleaks, all versions

[Joe Julian]

I don't think "unfortunatelly with no attraction from developers" is 
fair. Most of the leaks that have been reported against 3.7 have been 
fixed recently. Clearly, with 132 contributors, not all of them can, or 
should, work on fixing bugs. New features don't necessarily interfere 
with bug fixes.

The solution is to file good bug reports, 
https://bugzilla.redhat.com/enter_bug.cgi?product=GlusterFS , and 
include valgrind reports, state dumps, and logs.

This is a community, not a company. Nobody's under an obligation to 
prioritize your needs over the needs of others. What I *have* seen is 
that the more effort you put in to identifying a problem, the easier it 
is to find a developer that can help you. If you need help, ask. It's 
not just developers that can help you. I spend countless hours on IRC 
helping people and I don't make a dime off doing so.

Finally, if you have a bug that's not getting any attention, feel free 
to email the maintainer of the component you've reported a bug against. 
Be nice. They're good people and willing to help.

On 08/25/2016 12:26 PM, Piotr Rybicki wrote:
>
>
> W dniu 2016-08-24 o 08:49, feihu929 at sina.com pisze:
>> Hello
>> There is a large memleak (as reported by valgrind) in all gluster 
>> versions, even in 3.8.3
>>
>
> Although I cant help You with that, i'm happy that some one else 
> pointed this issue.
>
> I'm reporting memleak issues from some time, unfortunatelly with no 
> attraction from developers.
>
> To be honest, i'd rather see theese memleak issues addressed, than 
> optimisations/new features.
>
> Best regards
> Piotr Rybicki
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-users