[m a d r a]

since installing MX 2004, i have on two occasions had an alert popup in panther telling me my [2GB] swap partition is full and i must force quit apps to free up some application memory. on both ocassions this has happened after flash MX 2004 has been running for several hours. [in fact not even necessarily when flash is being used - this has happened when the comp has been left unattended for a couple of hours while flash is running].

when this happened last night, i launched 'activity viewer' and found that, although it was only using between 15-35MB of real RAM, flash was using a ridiculous 1,09GB of virtual memory; ie. filling the whole swap partition single-handedly.



has anyone else seen this kind of VM 'greed' with flash MX2004, or is this problem somehow related to the fact i have moved my VM swapfiles under panther to their own disc partition? [shouldn't be - the OS should take care of creating and removing swapfiles.. but you never know!]

[pismo 500MHZ, mac OSX 10,3,2, 640MB RAM, VM on dedicated 2GB partition].

[theolein]

Have you looked at the Macromedia forums to see if anyone else has seen this? The forums and error pages at Macromedia, in contrast to their applications are quite good.

[m a d r a]

yes. i've posted this on the macromedia forum as well. there were quite a few threads there about memory leaks with flash player, but nothing about the authoring app itself. looks like it's some kind of problem across the whole flash MX 2004 authoring and playing setup.

it's a pity adobe have taken livemotion out the back and put a bullet in its head. even tho' it wasnae much kop, a lot of us hoped that the competition might have give macromedia's design team a well-deserved boot up the arse.

[suthercd]

I know that Panther cleans up swap files, but do not know the parameters for when it does this. How did you move them..hard link, soft link??

Craig

[m a d r a]

i used this method. it's all greek to me, but i didnae have any probs with it until flash came on the scene.