I'm running Win2K and several times I've seen 40-50MB in the javaw process
and it's taking most of my processor cycles, usually after the node's been
running for a few days. A restart of the node seems to fix the problem and
sometimes it seems to fix itself. I'm just running the node, not actively
using it. I haven't noticed that characteristic in the last week or so so
maybe it's been fixed.
Fred
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Mark J.
Roberts
Sent: Wednesday, December 27, 2000 15:07
To: [EMAIL PROTECTED]
Subject: Re: [Freenet-dev] Map files for FProxy / Pissing Memory Down
The Drain
...snip...
Well, that's all working great for me now. The only problem is that FProxy
leaks memory so terribly that it would be impossible to surf Freenet for
more than 10 minutes without swapping and thrashing.
PID USER PRI NI SIZE RSS SHARE STAT LIB %CPU %MEM TIME COMMAND
444 root 9 0 87460 73M 380 S 0 0.0 59.9 0:00 java
(I have 128 megs of RAM!)
This is fucking unbelievable. I want to kill somebody. At first I thought
it was my fault, and after fooling around with my code for an hour, I
checked out a fresh, unaltered tree -- and it was EXACTLY THE SAME!
(Actually, Mr. Bad's SSK subspace, with about 10-15 images, leaked about
the same as or a little more than my hashtable in a mapspace with 35
images (full shift-key reload for both). This is strong evidence in favor
of MSKs.)
Is this the fault of SimplifiedClient and ProxyClient? Brandon, do you
have any idea what's causing this? Should someone who knows a lot about
memory and Java rewrite SimplifiedClient or something? Or is this a bigger
problem?
--
Mark Roberts
[EMAIL PROTECTED]
_______________________________________________
Freenet-dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/freenet-dev
_______________________________________________
Freenet-dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/freenet-dev