Re: Memory usage on Win32: Euphoria usage vs. what Task Manager displays
- Posted by AndySerpa Jul 31, 2009
- 989 views
Anyway, not only did it not free the RAM, but it used way more of it too. With the same code as before (my code, with the loops), when the counter is at 50 I get: 878,522K used, 200,000K more than before! And it doesn't free it either. After setting x = 0 (or x = {}, no difference), it only goes down to 780,696, still 100K more than the 3.1 version used maximum.
What are you using to measure this? I'm not seeing this effect at all.
Task Manager process list, Mem Usage column for exw.exe (eui? what's that?). I also have a "free ram" meter in my taskbar that shows available RAM and I can see the effect there.
And just to prove it isn't available to other apps, I can...well, prove it. I have 2 gigs of ram. So going by my FreeRam tool it shows about 1.25 gigs are free before running the program. Running this program on v4 drops that to about 411MB free. Then when I supposedly release the memory, I get about 90 MB back, so it shows 500 MB free. So, if that's true, and I now run another instance of the program without closing the first one, it should quickly eat up all my available RAM and drive the system into the ground. But if you are right, it should be able to re-use the memory from the first process and everything will be fine.
But, running that second process does run the system into the ground. FreeRAM quickly drops to zero. Watching in the task manager, process1 holds its RAM absolutely steady at 780,000 or so. So process2 still needs plenty more and is struggling to get memory, and now you see all the other processes on the system start to drop their RAM usage, presumably as it is swapped out to the paging file so process2 can use it. So we can see process2 slowly gaining RAM at this point, and all the other processes dropping EXCEPT the Eu process1, which STILL is holding on to every byte! Diabolical!
