Hi, Does anyone have any thoughts on this?
Is it normal for memory to fluctuate when there are no user interactions (or timers or anything else in the code)? With the exact code I included I had the following behaviour: initial memory: ~4.5 MB for a few hours: the memory would cycle up to about 6.5 MB before garbage collection would kick in and it would go back down to ~4.5MB The next day: Memory had hit a max of 29.5MB and even using the hack to run garbage collection wouldn't bring it below 26MB Is there a fault in my code, is this a bug or is this just the normal behaviour for an application? Any feedback would be welcome! Bill --- In [email protected], "beecee1977" <[EMAIL PROTECTED]> wrote: > > Hi, > > I've been having memory problems with my application when it's left > running overnight in IE7, which often results in IE crashing and a > flash9.ocx error popup. > > Anyway, I'm struggling to pin down where the problem is coming from. > I know about the seemingly whimsical nature of when garbage > collection is done, but even still this behaviour seems strange to > me: > > (See the sample project below) With just a VideoDisplay object > playing video (or paused!) the memory will keep going up for a couple > of Mb at least. At some stage the garbage collection will kick in and > it will recycle, but is this normal/expected behaviour. It looks > funny for my application, which is very video reliant, to have the > memory constantly fluctuating even when the user is doing nothing. It > also makes debugging for my memory leak very tricky. > > Does anyone have any advice for tracking down my problem? Would it be > making a difference that I have the debug version of flash? > > Here's the sample app (not very neat) that demonstrates the problem. > Just click "Load" followed by "Play/Pause" and watch the memory go. > Sometimes if I click about on the slider or pause and play or even > just leave it for a while the problem becomes more pronounced. (Also > using the add/remove buttons to add extra components doesn't seem to > cause the garbage collection to occur) >
