Topic: Available Memory and Flash Lite memory leak
If you've programmed for Flash Lite 2.x, you're probably familiar with this command, which returns remaining available heap memory:
fscommand2('GetFreePlayerMemory')
On mobile devices based on BREW or Symbian, the total memory available to the Flash Lite application typically starts at 2 MB, and goes down as the program runs.
On Chumby (at least the one I got my hands on) the memory starts at 8 MB, which is great.
However, the above command doesn't seem to return accurate values on the Chumby. I did a test where I had it load a jpg when I press a button, and every few milliseconds I update the display of free available memory. The problem is that the free memory display didn't change, even after the (large) JPG loaded. Is this a known issue?
It's important to know and follow the memory situation during development of Flash Lite applications. On mobile devices, this is a BIG issue. It's even a bigger issue because the Flash Lite player from Adobe seems to have some memory management problems, and their garbage collector doesn't always work. (If you only create desktop/browser apps, then you wouldn't know or care about this.)
I would very much appreciate it if the person at Chumby Industries who ported Flash Lite to Linux commented on the GetFreePlayerMemory command.
Is it supposed to work properly?
Are you aware of the memory management problems in Adobe's code, and were you able to spot and fix any of them? (One problem area is their XML parser.)