Garbage Collection doesn't always collect everything right away so memory
might look like it keeps going up but should eventually hit a cap. There is
a hack involving LocalConnection you can try to force full collection, but
if there is no leak, you should be able to run the app all night and memory
should eventually stabilize, although maybe at a bigger number than
expected. If you run out of memory, then something is still wrong.
Thanks for the fast answer.
So you think there is no mistake in the code?
In my application memory is rising and rising i left it for a few hours and memory was still rising...
Can you explain the "hack" a little bit more?
And is there an alternate which won't need so much memory?
Thanks in advance
Look up localConnection hack.
You can always skip HTTPService and use the lower level URLLoader