On Fri Oct 17 16:21:09 2003, davem wrote: > The short answer: doing anything from a DESTROY method during global > cleanup is always risky, as you don't know what else has already been > cleaned up. > > The long answer: Storable has private "context" data structures which > it allocates as needed by creating an object SV and typecasting the > object's PVX (of the right size) to store this structure. > During global cleanup, these object(s) are freed, so you end up with > contexts accessible in freed memory. I don't know enough about > Storable, > and what it uses its contexts for,and why it sees fit to allocate them > from PVs, in order to feel confident in trying to fix this. If Memoize::Storable were to fire its destructors preemptively in an END block, that would eliminate the crash (untested). Should Storable itself also be made more resilient?Thread Previous | Thread Next