As I (and I'm sure others) mentioned before, my node is still going
down (crashing?) regularly -- roughly weekly. I currently allocate it
150MB of (precious) ram. Here are my last 2 (of infinity) heap reports
from the jvm dump:
Heap
def new generation total 46080K, used 41323K
eden space 40960K, 100% used
from space 5120K, 7% used
to space 5120K, 0% used
tenured generation total 102400K, used 99586K
the space 102400K, 97% used
compacting perm gen total 12288K, used 11390K
the space 12288K, 92% used
ro space 10240K, 61% used
rw space 12288K, 60% used
Heap
def new generation total 46080K, used 41400K
eden space 40960K, 100% used
from space 5120K, 8% used
to space 5120K, 0% used
tenured generation total 102400K, used 102399K
the space 102400K, 99% used
compacting perm gen total 12288K, used 11214K
the space 12288K, 91% used
ro space 10240K, 61% used
rw space 12288K, 60% used
Is there NO way that freenet can do a better job cleaning up? (I
believe this happens even if I don't have (much) currently in the queues
-- Ie. if I did heavy activity days before -- or maybe even on it's own
without any manually-initiated activity, although I would have to test
this more :\.)
Maybe we can add more debugging info as to where all the memory is
allocated? Ie. which structures? (And hopefully decide that we can Let
Go of some of them :|.)
_______________________________________________
Support mailing list
Support@freenetproject.org
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:support-requ...@freenetproject.org?subject=unsubscribe
