I have noticed on two Windows XP computers running a modified Gnucleus 1.5.2.0 that after a day or so the program starts to 'lag'. The modifications I made where very small. I just hard-wired some options in, removed some options from the preferences dialogue, and changed graphics.
I also noted that the program was taking about 50% of my PIII 450 with 256Meg memory after running for so long. I closed the program and started it up again...good as new. Oh, and there where no downloads going and only 6 connections. Any suggestions? Here is a clip of the crash I got while trying to close the program after a day of use: The instruction at "0x00000001" referenced memory at "0x00000001". The memory could not be "read".
I'm running in LAN mode...maybe the next version will fix this.

-Matt
matt@mattjanssen.net

I have had the same error durring a crash. However, I've not seen it use a large percentage of the processor.

Buck

I think the way most any Gnutella app thrashes the winsock you're likely to have problems after several days running. Gnutella is just very, very resource intensive due to all the connections it goes through.

Another possibility is Gnucleus keeps a lists of things like failed uploads/downloads etc. I don't know if there's any limit to the size they can grow, and they must take memory. I know they can grow so big as to really overload the list box when you try and display them.