Quote:
It could be the C(++) runtime or the operating system keeping the memory ready for the Reaper process in case a new allocation is going to happen in the near future anyway.
|
If that is the case that would be problematic cause a script of mine reach memory limitations (it scans a lot of file) and there would be no way to free the RAM back... :S
@mespotine
I tried and there seems to be some success if you reset the variable before that like
Code:
a = ''
collectgarbage()
It works only if the IDE is open, as this seems to be even more problematic in this case.
But for real life situation with complex loops etc, this cannot be a valid solutions, it will litteralu double the code line count... +, I didn't found any success on my complex script, only on this small snippet.
I think this memory issue should be handle by REAPER itself.