Hi Ulrich, > >you mentioned that you're debugging an other problem. Is it possible that >you're mixing >debug and release binaries? E.g. debug build of your project with OSG release >libraries?
Thanks for your fast reply! In fact, I did not debug *another* problem, but the described heap damage error. However, I checked the configuration of my Visual Studio project and stated that the corresponding debug/release binaries are linked. Both debug and release build of my program produce the heap damage error. So, I could not solve the problem yet. But additionaly, I found out a memory leak that takes place, even if I run my program without pushing extension strings in getRequiredExtensions() (and thus without a crash). The memory leak is 248 bytes long and takes place, if I register a prototype of the MyCartoon class with Registry::Proxy proxy(new MyCartoon); as in the original osgFX files. I could not figure out, which object rests in memory there, because the destructors of the Registry and MyCartoon instances are invoked correctly. If I omit the registration, the memory leak doesn't occur. I have no clue, if the heap damage error relates to the memory leak. Has someone further hints or experiences regarding these problems? Cheers, Matthias Schütze, Germany ___________________________________________________________ Schon gehört? WEB.DE hat einen genialen Phishing-Filter in die Toolbar eingebaut! http://produkte.web.de/go/toolbar _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
