Sep-20-2016, 05:28 AM
(Sep-19-2016, 02:02 PM)Kebap Wrote: The garbace will not be collected immediately when you call it, but at some arbitrary time, which can't be influenced directly. It depends on many things, maybe that is why you see the slow build-up and sharp decline there. By the way, which concept are you proofing? :D
We started doing something about memory in my CS class, and then I had maths where we had some graphing exercises. I was wondering if what I want to do is possible. That's really it :P
(Sep-19-2016, 07:00 PM)Ofnuts Wrote: Doh... Now I understand what you want... Highly unlikely to work. Even assuming that the GC actually does something when you call it, it won't always return te recovered memory to the system.
Ok, I seem to understand. I've read here(https://stackoverflow.com/questions/1545...-in-python) that if I spawn child processes, it shoudl release the memory back to the system. Another alternative I have thought of is making a 2D array, where each row is a diffferent length to correspond to how much memory must be used, and then deleting the rows in such a way that they create a sine curve. However, I don't know if I could get around the garbage collector issue that way :/