While profiling the block of my classes, I noticed that the String class accumulates infinitely (eats up more than 90% of the memory in my significant application). Fortunately, this is only while working in Profiler Flash Builder 4.6 mode. When debugging or deploying (as in AIR), memory usage levels are disabled as expected using the built-in memory profiles on the screen (Mr. Doobs Stats).
To verify that I made a test application that was just URLLoader, constantly downloading a text file. When working in Profilier mode using URLLoaderDataFormat.String, String data is never GC'd and does not grow continuously, and using URLLoaderDataFormat.BINARY, the data is almost immediately GC'd and remains level.
I hesitate to call it a mistake, because maybe it is necessary for the Profilier part to work ... but maybe this is not normal for Profiler? This is the essence of my StackOverflow request.
Anyway, this burned a couple of working days for me, so if you search Google why the String class grows crazy and never collects GC'd, think about measuring the memory usage of applications outside of Profilier to check. In my case, I was mistaken in thinking that I had a problem with Master Strings - although Master Strings understands this well and their effect on memory ( see:) do not be misleading like me.
source share