[Papervision3D] Memory leak

[Ralph Hauwert]

Hi Pedro,

Actually, I've implemented destroy not to be called by the engine, but  
by the programmer; for instance with coverflow like apps, where you  
need to get rid of old materials on the fly. Since we can't do the  
reference counting in AS (or keep track of where those references come  
from), this will be a hard process to fully automate within  
actionscript.

.destroy() and it's implementation is by no means final, but I don't  
think we can do this automatically without limiting people with other  
implementations.

Ralph.

On 19 feb 2008, at 11:38, Pedro Furtado wrote:

> Hey dudes,
>
> I just came across a nasty memory leak in my materials, the problem  
> was with the destroy method not being called. I haven't had the time  
> to dig deeper into the engine's code but until then here's a small  
> workaround
> http://www.dreaminginflash.com/2008/02/19/papervision3d-gw-memory- 
> leak/
>
> -- 
> Pedro Furtado
> http://www.dreaminginflash.com  
> _______________________________________________
> Papervision3D mailing list
> Papervision3D at osflash.org
> http://osflash.org/mailman/listinfo/papervision3d_osflash.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://osflash.org/pipermail/papervision3d_osflash.org/attachments/20080219/9cc9b3d6/attachment.html