Re: ustring memory leak

[michi7x7 <mailing-lists michi7x7 de>]

> > From the small ouput you pasted above, the "leak" seems constant, i.e,
> it doesn't grow with time, and it doesn't grow with the number of
> threads created and then destroyed, does it?
> If so, it would rather look like some memory allocated once -- by the
> Glib treading machinery -- and that is not de-allocated.
>
> Is that really worrisome?
>    

It is, because the unused memory is growing all the time.
Don't forget this line which is called every 1000 thread-instances:

lastMem = currentMemory;