I am looking at integrating the SfRotator into my app however when working with the sample, if I scroll through images around 20 times, then I receive an out of memory exception. This occurs more or less frequently depending on the size and number of the images used. 20 times is using the 5 Movie PNGs as provided in the sample.
I subclassed the Image class, and then put a break point in the constructor of the class and found that the new objects are created for each scroll, therefore it doesn't look like there is any caching being employed for the SfRotator.
Is there a work around for this or will this require a service release?