|
Matt Burch
post date:
2008-05-21 10:33:20
|
We are attempting to implement your product in a major project we're working on, and I saw something that may be a problem. The project is a bit like a slideshow, every 30 seconds a new SWF is transitioned in. After letting it run throughout the night, its memory usage doubled from 40MB to 80MB. We're not loading anything but simple SWFs, no special assets like sounds or BitmapData.
Since MovieFX uses BitmapData objects to do alot of the effects, I checked in the supporting classes. I was shocked to see that none of the local BitmapData objects being created are being properly disposed. I'm really hoping that the development team ensured that these BitmapData instances were being properly disposed somewhere in the component after an incoming effect is finished, or that there's an undocumented method in the API for us to dispose of internal BitmapData instances.
I've been using MovieFX for several weeks with this project and don't want to backpeddle, but if common memory leak risks weren't addressed, I'll unfortunately have no choice. Thanks for your time.
|
|
|
Horea Radu [Extend Studio]
post date:
2008-05-27 04:19:38
|
Hi,
The bitmap objects are not distroyed because the effect assets are used when the effect is reversed or replayed, operations that a user might want to do without having to recreate the effect assets each time.
Unfortunately, the current version does not implement a method that disposes the BitmapData objects. This will be implemented in the next version of MovieFX.
Best regards,
Horea RADU.
|
|
