12
Replies
Well... we're definitely getting closer! 
Ok, so the issue I'm seeing now is what appears like inadequate garbage collection.
I'm using readBytes( myByteArray, startPos, sliceSize);
This provokes the continuation of the read (otherwise the read just stops... which is great!)
However, one of two things happen.
Either I don't re-initialize myByteArray in the process, in which case I run out of memory around 640 megs
or, before every read I declare:
myByteArray = new ByteArray()
and this allows me to get to around 1.8 gigs before the system runs out of memory... presumably because the garbage collector isn't keeping up? (I'm guessing obviously).
So the question is... what did you do to vacate that container in your test, or did you use something other than readBytes and if so, what was it?
I'm attaching my code snippet just so that you can tell me I'm doing something wildly stupid (if I am).
private var total:Number = 0;
private var b:ByteArray = new ByteArray();
private function onBytesRead(e:ProgressEvent){
if(e.currentTarget.bytesAvailable >= chunk){
trace("avail = " + e.currentTarget.bytesAvailable)
trace ("read " + (total += e.currentTarget.bytesAvailable * 1));
b = new ByteArray();
e.currentTarget.readBytes(b,total, chunk)
}
}
//called when user selects a file
private function selectHandler(event:Event):void {
var file:File = File(event.target);
stream = new FileStream();
var f:File = event.target as File;
stream.addEventListener(ProgressEvent.PROGRESS,onBytesRead);
stream.readAhead = chunk;
stream.openAsync(f, FileMode.READ);
}
AdChoices