No subject

to
the container, so it cannot unlink the bucket. 

Because the bucket is still there, and points to unallocated mem,
subsequent memory allocations will re-use the space, and searching for key
"A", which would otherwise yield no match, trips over garbaged memory and
the process aborts.

This is not an unusual situation.

My personal guess is that memory should not be freed in ao2_ref(), and
that buckets with 0 refs need to be purged in more places. Actually, every
possible operation that might bump into them at the container level. This
is a bit messy.



====================================================================== 

---------------------------------------------------------------------- 
 russell - 09-07-07 12:40  
---------------------------------------------------------------------- 
I don't think this is correct.  This free() will never occur if the object
is still in a container.  The reference count includes a reference for each
container it is in. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
09-07-07 12:40  russell        Note Added: 0070119                          
======================================================================