Memory use, forcing GC, %oXX vars keeping references
Subject: Memory use, forcing GC, %oXX vars keeping references
From: Daniel Lakeland
Date: Sat, 20 Jan 2007 10:38:36 -0800
I've been using the "rk" function with very small step sizes, I tend
to get back lists of several thousand or a million entries.
After a while, gcl eventually crashes. I'm running on an AMD64 machine
with 2G of memory, but I'm not convinced that gcl is able to use the
entire address space since it tends to stay below about 500MB before
crashing. I do "kill(solns)" (the variable that stores the output) at
each iteration, but I'm thinking perhaps that the %o1,%o2 type
variables keep a handle to these big lists so they aren't gc'ed.
Short of manually typing in kill(%o42) and soforth for each iteration,
how can I ensure that these lists get GCed and hence keep my system
running longer between crashes (maybe)?
--
Daniel Lakeland
dlakelan at street-artists.org
http://www.street-artists.org/~dlakelan