On Wed, Feb 23, 2011 at 2:02 PM, Kurt H Maier <karmaf...@gmail.com> wrote: > On Wed, Feb 23, 2011 at 2:40 PM, Kris Maglione <maglion...@gmail.com> wrote: >> it wasn't a leak. > > On Wed, Feb 23, 2011 at 2:40 PM, Kris Maglione <maglion...@gmail.com> wrote: >> the free list grew without bound > > what > > > -- > # Kurt H Maier > >
Leaked memory is allocated but unreachable, the result of failing to free a dead block. In this case, the fault was increasing the size of a memory pool without the pool manager's knowledge. It happened to result in the same failure that a memory leak would cause, but the two fault types are still distinct. -- Steve McKay
