search

thcmedia / papervision3d

Automatically exported from code.google.com/p/papervision3d
0 stars 0 forks source link

one step removal/clean/destroy method #51

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. create a scene
2. add objects
3. remove the scene, container, clear all external references, etc...

What is the expected output? What do you see instead?
The whole PV3D instance should be cleared from memory. Instead, the scene
stays in memory, along with all its objects and materials, thus using CPU
and slowing performance.

What version of the product are you using? On what operating system?
GreatWhite

Please provide any additional information below.
I propose a detroy method for the view, scene, viewport or whatever, that
takes care of clearing the whole papervision instance... I was able to
clear all objects and materials (after a few hours of looking around the
API) and the memory leak now is much lighter...

Original issue reported on code.google.com by ventda...@gmail.com on 9 Apr 2008 at 2:43

GoogleCodeExporter commented 8 years ago 
One step would be a bit hard, but most removal / destroys are now handled..

Original comment by r.hauw...@gmail.com on 8 May 2008 at 10:24