Re: trigger GC before memory limit is exhausted

On 19 May 2015 at 14:28, Rowan Collins <rowan.collins@gmail.com> wrote: > Dan Ackroyd wrote on 19/05/2015 14:08: >> >> * When gc_collect_cycles is called (and potentially other functions), >> at the end of that function check whether the amount of memory being >> used is less than reset level for each trigger. If so reduce the >> current memory limit to the lowest trigger level. > > > The only flaw I see in this approach is that the majority of memory > deallocation is done transparently be the ref-counting mechanism, not any > particular function, and the user should be able to trigger this manually. Good point, I'll think about that. Danack wrote: > I'll wait for some feedback, then write an RFC Actually no I won't, I'll try to implement it as an extension first. cheers Dan