Let me see if I can shed some light on this subject for you guys.
Pay attention WGT, since you willfully disregard helpful emails
suggesting how to fix the memory issue. You would never take advice from
a former Adobe Computer Scientist, would you? Because, What does he
know? Right?
When any Adobe Flash app. frees a ByteArray, the reference to the array is erased from the domainMemory object, but when the free is done by a worker (a virtual instance of the Flash runtime. Each worker instance controls and provides access to the lifecycle and shared data of a single worker.), then the domainMemory is never informed and you have what is commonly called a Dangling pointer (a pointer that does not point to a valid object of the appropriate type.)
A worker allows you to execute code "in the background" at the
same time that other operations are running in another worker
(including the main .swf's worker). In a non-worker context, (some
operations), i.e., processing large sets of data in a loop, take so long
to execute that they prevent the main application thread from updating
the screen quickly enough. This can cause stuttering or freezing the
screen and the White / Blue Screens the members are getting.
Dangling pointers come about during object destruction, when an object that has an incoming reference is deleted or deallocated, without modifying the value of the pointer,
so that the pointer still points to the memory location of the
deallocated memory. The system may reallocate the previously freed
memory to another process, if the original program then dereferences the
(now) dangling pointer, unpredictable behavior may result, as
the memory may now contain completely different data. This is especially
the case if the program writes data to memory pointed to by a dangling
pointer - a silent corruption of unrelated data may result, leading to
subtle bugs that will be extremely difficult to find.
Hint: ByteArray : : Clear ( )... You guys should know the remaining code without me posting it in here. (CLEAR YOUR CACHE, in your own words.)
The game is overfilling our gas tanks and now fuel is spilling out
onto the driveway because someone wasn't standing by the nozzle. That's
why we are all getting the dreaded Flash memory ! overload.
just sayin'....
Back in my hole, I go.