Hello all: I am trying to run down a memory bug in my application. I think OpenSG is somehow getting ahold of a deleted object, but I am not sure.
I had added some code to help with this type of issue a year or more ago using the OSG_ENABLE_MEMORY_DEBUGGING setting. As I remember, this would check that objects are valid as part of commitChanges() calls. What I was wondering is does anyone know how we could extend this further? Perhaps making dereferencing in all the XxxPtr types check that the fc is still valid? If we had that, then I think it would stop the application in it's tracks the first time it tries to use an fc that is not valid anymore. Would this work? How could it be implemented? (I currently have a _check_is_deleted() method on OSGReflexiveContainer, but I am not sure if that is the best place) Any other ideas? -Allen ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Opensg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-users
