I've been running into some memory limitations in a flex application that I'm working on. As a test I wrote the code below to try and determine what the true memory limitations of a flex application running in the flash player are. What I've found is the following. On both the windows and linux machines there is a total of 4G of space available and in none of these cases was the OS near hitting the physical memory limit.
Max memory usage on various configurations:
flash player 10 on windows = ~650M
flash player 9 on windows = ~800M
flash player 10 on linux = unlimited (I was able to get up to 2.5G without any problems)
Has anyone else run into these limitations? Can anyone comment on possible work arounds to these limitations or provide any insight on why the flash player would have an artificial memory limit below what the OS can provide?
In the following application each button click takes up about 100M making it fairly easy to see at what point the flash player is crapping out.
<?xml version="1.0" encoding="utf-8"?>
<mx:Application
xmlns:mx="http://www.adobe.com/2006/mxml"
minHeight="600" minWidth="800">
<mx:Script>
<![CDATA[
import mx.formatters.NumberFormatter;
var outer:Array = new Array(1000);
var outerCnt:int = 0;
private const MBYTE : int = 1024 * 1024;
private function onButtonClick():void {
var inner:Array = new Array(5000000);
var formatter:NumberFormatter = new NumberFormatter();
formatter.useThousandsSeparator = true;
var cnt:int = 0;
for(var i:int=0;i<50000000;i++) {
inner[cnt++] = "testsstringtestsstringtestsstringtestsstringtestsstringtestsstringte stsstringtestsstringtestsstringtestsstring";
}
outer[outerCnt++] = inner;
text.text = formatter.format(flash.system.System.totalMemory/MBYTE);
}
]]>
</mx:Script>
<mx:Button id="btnConfirmSubmit" click="onButtonClick()" label="click me"/>
<mx:Text id="text"/>
</mx:Application>
