Has anyone else noticed Xolox freezing after running for a while? Or is it just me. I am running Win2K

I've been running it on WinME and after a while it starts to behave erratically and eventualy freeze. Immediately afterwards my WHOLE system starts to freeze. I'm using ver. 1.11 and I think it has a resource leak. If I open Xolox and then minize it to the tray and then restore it a few times (4 times is enough) I notice that my RAM and system resources get used up VERY quickly. I've tried this even with a clean boot and no apps running (using MSConfig) and it still keeps on happening. I know it's not the system because it works fine and I have ALL the latest drivers, updates, and patches.

One more thing... Xolox ver. 1.11 is using OVER 60% of my CPU time! on an Athlon 1200!!! What gives????

Go to http://xolox.gnutelliums.com and get 1.12. It fixes the '1 thread per (sub)directory shared' oversight, and seems to be a bit more stable.

I am using XOLOX ver 1.12 on WIN98 and have found that it freezes my system about every 5 minutes or so. I never had this problem with the previous version of XOLOX and was very unhapy that the upgrade self-installed without my permission. This is a lousy so called upgrade!!

You can disable the autoupdate option in preferences, for win2k users 1.12 seems to be an improvement. Only time will tell

Ok,
I did have 1.11 working, and I survived the hostlists problem, but now with 1.12 I get "Invalid class string" errors.. This is a shame, as I was pretty happy with the behaviour of xolox.

I have win 2k, 7xx Mhz pentium II

Anyone else get this error ?

Richard

On the note: WinME itself has a memory leak issue. Not giving back memory after a program closes.
I'm running Win98 myself on a Athlon 500Mhz with 128Mb and can run XoloX for days without crashing. Only when closing XoloX it may occasionaly crash. On the system resources:
While downloading multiple divx files I'm able to watch a Divx fullscreen without problems.
So I'm wondering what specific environments (eq. other programs running, amount of downloads, memory, OS, number of shared files etc..) people are running that are experiencing the crashes. Maybe the XoloX team can determine that way what is the dominant factor here and eliminate it.

Just a thought on this ... could it be an anti virus issue as I have seen some a/v progs grab loads when doing a default scan ?

just an idea