[prev in list] [next in list] [prev in thread] [next in thread] 

List:       taglib-devel
Subject:    Re: Possible memory leak || what I am doing wrong
From:       joseph Dobson <dobson156 () gmail ! com>
Date:       2011-09-06 10:17:57
Message-ID: CAH9WD8-aAQ2Q=rDQYsTBc+Hen23H0pXovp4A7hH4AGyPpWfYrQ () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Thanks you for taking the time reply, perhaps this should be put in the docs
or something indicating that it will leave this memory. (sorry if it is).

Or ideally could there be a cleanup function or anything of that nature that
can be be used to destroy the singleton?

I know it is probably okay to leave reachable bytes, but it would be much
easier for developers using your API to not have to deal with this as it
clutters up the valgrind output.

I don't mind making these changes to your code, if you would be interested
in having them in your code base.

Thanks Again

[Attachment #5 (text/html)]

Thanks you for taking the time reply, perhaps this should be put in the doc=
s or something indicating that it will leave this memory. (sorry if it is).=
<div><br></div><div>Or ideally could there be a cleanup function or anythin=
g of that nature that can be be used to destroy the singleton?</div>
<div><br></div><div><div><div><div>I know it is probably okay to leave reac=
hable bytes, but it would be much easier for developers using your API to n=
ot have to deal with this as it clutters up the valgrind output.</div><div>
<br></div><div>I don&#39;t mind making these changes to your code, if you w=
ould be interested in having them in your code base.</div><div><br></div><d=
iv>Thanks Again</div><div><br></div></div></div></div>


_______________________________________________
taglib-devel mailing list
taglib-devel@kde.org
https://mail.kde.org/mailman/listinfo/taglib-devel


[prev in list] [next in list] [prev in thread] [next in thread]