Subj : Re: Valgrind reported memory leak
To   : comp.programming.threads
From : Sean Burke
Date : Wed Jun 08 2005 05:58 pm


"Peter Dimov" <pdimov@gmail.com> writes:

> Sanket Shakyavanshi wrote:
> > I have tested the same scenario with longer run and with more
> > connection handle, but didn't observe more leaks. This is one time
> > leak.
> 
> The leak is probably caused by a statically initialized mutex. One-time 
> allocations that are never deallocated are typically harmless. "Leaking" 
> usually refers to the process gradually eating an unbounded amount of 
> memory. 

I once had a rather lengthy discussion with someone about
whether it would be a good idea to register an atexit()
handler to "fix" a "memory leak" similar to this one. 

-SEan

.