Howdy. I have a rather large AIR 1.5 app. It is using the FileStream.openAsync method to open a number of files (50-100). Initially I coded it to just loop through all the files it needed to load in one loop calling a loadFile method that setup the FileStream with openAsync and then called readBytes in the completion function for openAsync. It works-most of the time. I have a separate window that I send debug trace-like messages to and I see it loop over the files and call openAsync for each of them. It then reaches the readBytes portion and successfully reads most of the files.
The problem I am having is sometimes it never reaches the completion method where I call readBytes for some of the last files. Nor does it throw any exceptions or errors. It’s as if the call to openAsync succeeded but the actual open command never executed.
Oddly, when I run it in the debugger it usually opens all the files successfully, leading me to believe this is somehow timing related. It isn’t a scoping problem, the class that encapsulates all this remains in scope and not garbage collected throughout the life of the application.
I got to thinking that queuing up 100 async file operations may be too many for the AIR runtime to handle. It seems when I limit it to smaller chunks it works OK. I don’t mind refactoring this code to work in chunks of smaller groups of files, but I hate changing things without understand WHY I need to change it. It is POSSIBLE that there is some subtle bug in my code, although I have stripped it down to the bare essentials and have watched it call openAsync for all files.
Any thoughts???
