Hi everyone,
While experimenting with a customized MegaZine interface (by loading megazine.swf into a custom shell, suppressing the built-in navigation, then adding my own nav and communicating via events), I noticed that the RAM usage for my 64-page book kept growing more than I expected as I flipped back and forth, even when setting the maxloaded attribute to 64.
To test if my custom code was a contributing factor to the RAM usage, I put aside my version and downloaded the standard v1.38 zipped binaries, just modified the XML to load my SWF pages, then ran the results in IE 7 and Firefox 3 with non-debug versions of Flash Player 10.0.32.18 under 64-bit Windows Vista. (The SWF pages were produced by the pdf2swf component, and no videos were added.)
With maxloaded set to 64, memory usage at initial load climbed to 153-183 MB after all pages seemed to be loaded. Then, as I flipped through each page of the book to the end, RAM usage grew to between 285-350 MB. When I started skipping around and going back through the book, memory usage started increasing further. Repeating the above with maxloaded set to 12, RAM usage got to 400 MB fairly easily. Again, this was just with the standard v1.38 binaries and my own SWF pages, no custom code.
Am I missing anything obvious to try to stabilize if not limit the memory consumed by my 64-page book? Putting aside any potential interface customizations, I had hoped that setting maxloaded to 64 would result in an initial maximum allocation that wouldn’t increase (much) as I navigated between pages. Or that setting maxloaded lower would allow older pages to be released from memory as I navigated forward. Any recommendations, suggestions or workarounds are greatly appreciated!
Thanks in advance,
Brian
