Are you trying to sending multiple requests to a server within one frame? This seems kind of crazy anyway - what information on the server is changing within a fraction of a second? It sounds like you want to be using an interval (see setInterval) or an onEnterFrame event to trigger your requests to the server. I'm not surprised that requesting multiple XML documents within a frame confuses the Flash Player and keeps it so busy it can't garbage collect. If you want real time updated data from a server then you should look into XMLSocket's and a socket server which could push the new data as it changed...

On 9/5/05, Nick Griffiths <[EMAIL PROTECTED] > wrote:

We've stopped developing on the timeline, and our  app seems to use huge
amounts of memory when left running for a long time.  I thought i'd
narrowed it down to XML parsing (server polling), so I set up a couple
of tests; one which sits on a single frame of a movie clip firing of
server requests in a for loop, the other which fires of requests every
frame.  The first test seems to use a huge amount of memory that is
never freed after (50 or so calls worth), while the second cleans up
every call and never goes over about 20mb.

I set up another test, a sort of mix between the two which did about 50
requests in a for loop, then moved along about 5 frames and a
key-frame.  The swf in this one seemed to garbage collect after the for
loop when leaving the frame which had the code on it?

So what I'd like to know is, has anyone else had any problems with flash
not garbage collecting as you'd imagine?  I've read somewhere that it is
done every minute, but that sounds pretty arbitrary.  I'm reasonably
confident I'm not causing the memory leak, but then I don't know enough
about the Flash VM to be certain about that (I once ready a spooky
article about flash scoping, esp nested functions).

_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org

Reply via email to