What I've heard about IE is that unfortunately even though the Player has released the memory it needs, IE often does not, so your system manager will show IE taking up lots more memory than the Player itself is using. If you check the flash.system.System.totalMemory property you'll see what the Player itself is actually using. Matt
________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Alex Harui Sent: Friday, March 16, 2007 10:55 AM To: [email protected] Subject: RE: [flexcoders] Re: Runtime Memory Problems I saw another email yesterday saying that there are some known bad behaviors with IE7 that are being investigated... ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of One Person Sent: Friday, March 16, 2007 10:26 AM To: [email protected] Subject: [flexcoders] Re: Runtime Memory Problems I might agree with that, but in Firefox this is not an issue. Firefox releases memory on a regular basis while IE7 does not seem to release until I exceed the physical memory on the machine. BTW: I posted the wrong sizes in my original email. The images we are dealing with are 256Meg to 600Meg and the application will get up over 2.5Gig and then free up memory. I have 2Gig of physical ram in my machine. Mike --- In [email protected] <mailto:flexcoders%40yahoogroups.com> , "Alex Harui" <[EMAIL PROTECTED]> wrote: > > GC is opportunistic. This means it does not run all of the time. It > tends to be triggered by allocating memory instead of freeing it, so > watching an idle app will almost never result in GC. > > > > A good test is to cycle between two images 1000's of times and see if > memory usage is unbounded. > > > > -Alex > > ________________________________ >
