I have an application that caches an object that contains a DOM_Document object. The application doesn't rely on the cached document, it just happens to be an attribute to this cached class. When the application retrieves this object from the cache, it attempts to update the document object (i.e. calling operator==) and core dumps because of the call to RefCountedImpl::removeRef dies if document was already destructed (even though the document was still in use). Are there any known bugs or issues with this logic? I can reproduce the problem in 1.5.1 and in 1.6.0 (I haven't tried 1.7.0). The problem is somewhat random, but reproducible. Any help would be greatly appreciated.
Thanks, Rich Christy [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
