http://livedocs.adobe.com/ Macromedia LiveDocs - online documentation with user feedback. Copyright 2009, Macromedia, Inc. 2009-11-25T03:59:39 en-us http://livedocs.adobe.com/flash/9.0/ActionScriptLangRefV3/flash/utils/ByteArray.html#69395 The memory leak on ByteArray operations is a shame insofar as ByteArray operations are exceptionally fast - almost as fast as the pre-built BitmapData operations (compare, threhold etc). <br /><br />And ByteArrays can be copied to BitmapData extremely efficiently (using BimapData.setPixels) providing a way of effectively implementing very fast custom BitmapData operations.<br /><br />In a test I did, a custom ByteArray version of the BitmapData.compare function was going nearly as fast (50%) as the BitmapData version. Which is pretty good considering I had more than just a compare going on in the ByteArray version . <br /><br />The memory leak could possibly be corrected by a delete/new on the ByteArray - ie. possibly forcing garbage collection of the read buffer but this won't help if your ByteArray is meant to stick around (eg. as a lookup table for the duration of an app). <br /><br />The only other solution I can think of is to store long term data in BitmapData objects - copying such to freshly instantiated ByteArrays - deleting the ByteArrays when done. This will, however, reduce the turn around efficiency but perhaps not too much. And not sure what the cost of re-instantiating ByteArrays will be - but given what appears to be the existence of internal read/write buffers - one assumes there is a minimum of these already allocated to handle fast instantiation. <br /><br />Carl Carl Looper 0 0 2007-07-02T15:56:37 http://livedocs.adobe.com/flash/9.0/ActionScriptLangRefV3/flash/utils/ByteArray.html#69348 I'm getting an eventual "system out of memory " after reading an otherwise very small ByteArray a large number of times. (performance testing)<br /><br />Error: Error #1000: The system is out of memory.<br /><br />There is some sort of memory leak going on here. The system must be reallocating a buffer for the array and the short turn around time (on the reads) is not giving the garbage collector enough time to throw out the old allocation. Or maybe I'm barking up the wrong tree. Carl Looper 0 0 2007-07-02T02:11:03 http://livedocs.adobe.com/flash/9.0/ActionScriptLangRefV3/flash/utils/ByteArray.html#68010 Why is it that the IDataOutput interface defined readShort() and <br />readUnsignedShort() while IDataInput only defines writeShort()? 0 0 2007-06-06T12:52:39