HI,
For the last 4 years I have been developing a touch screen interface and I've been having trouble with the screen that appears when a system is out of memory.... gray circle and white exclamation mark.
If I find memory leaks I could remedy them by nulling classses removing eventlisteners nulling vars ect. This seemed to keep memory leaks at bay. But lately Ive been getting the gray circle and not been able to see any obviouse memory leaks.
Could any other elements effect the amount of memory that is allocated to flash?
The flash sits with in VB7, VB7 I belive uses the internet explorer 8 plugin to display the flash.
I have a few questions...
System.freeMemory + System.totalMemory... This is the total memory given to flash to run the program with? freememory being whats left for flash to use? and totalmemory being the amount thats actually in use by the flash program?
Can the amount of total memory available to flash flucturate? i.e can a system take memory that was originally given to flash and use it some where else for example if microsoft word was opened could a system rob memory from flash's allocation to help support Microsoft word? I would assume this gives flash less memory to play with and make the chances of GCOD occuring more likely?
Ive read various reports that their is maximum amount of memory that a browser will allocated to flash? Is that correct? So how come if that max is say... 300mb I can create a memory leak and watch my commited charge in task manager sow up way above 300mb before I eventually get the GCOD?
If/WHEN we take flash out of vb7 and publish as a AIR project will this make life easier for me regarding memory?
Thanks very
Aidan