proper init and destruction
marcus.brinkmann at ruhr-uni-bochum.de
Tue Jan 29 14:07:57 CET 2008
At Tue, 29 Jan 2008 11:43:39 +0000,
Vassilios Zafiropoulos <vasili3000 at hotmail.com> wrote:
> this call uses only once some 1500 bytes that are never released. Is there something I can do about it? am i missing something on proper initialization and destruction of the library internal structures?
> also, in some other part of the lib i am debugging, successive calls to
> allocate up to 500 bytes that are never released. Do you have any clues on that?
Some results are cached statically in libgcrypt. This is not a bug.
A bug would be unbounded growth of memory allocations.
More information about the Gcrypt-devel