memory and cpu hog on win2k server

I had left xolox running for approximately 10 hours, with 3 searches running. Throughout this time, xolox used a good chunk of my cpu. At the end of this 10 hour period, xolox was using 100% of my cpu. After this 10 hour period, I tried to task-switch to xolox, and I was not able to switch to it. I decided to force windows to shut it down, after which doing so, appoximately 185MB of memory were cleared up.

There is something seriously wrong with this software.. I would think that it must be more than simple memory leaks. ?