This content has been marked as final. Show 3 replies
Just an update and the contents of the error alert message. The message in the alert reads:
"Out of memory loading member 42 of PLAYER·CAST 9, even after purging all purgeable castmembers."
It could have to do with your code since I have an app that will load in a couple hundred images while using copyPixels on each one and not hit the error that you are talking about, so I can't see 50 images creating the issue you are describing.
You can monitor you memory status by having the Window's Task Manager up when you start your application and make sure it is set to ontop always.
I've had a quick look into the memory usage using the Task Manager in XP and System Monitor in Win 98 - it seems, on XP at least, that the CPU usage for the pixelGet() and pixelSet() routines are not as demanding as I thought -some other routine may be causing the overload. However, the Kernel use goes straight to 100% when I start the projector on Win98 so I cannot see what happens - there are other metrics but I'm not sure just yet which to monitor and it seems that memory usage on Win98 differs from XP.
Thanks for your help - it's a start.