( only if you downloaded XoloX 1.5 before March 23rd. build 735 or before)

The 'silent bug' hopefully is fixed and your feedback would be great if you've had problems xolox closing on you.

It's a hard issue to isolate, but the coders have found the problem that COULD have been the cause. Important to note, this is a *beta* build

happy downloading!

Download the NEW build here:
http://www.xolox.nl/dl/new.asp

__________________
..got to have kaya

Confirmed that the problem has been fixed, at least on my system.

Thank you Targon, i hope there is some more feedback before proceeding to make it live to all.

__________________
..got to have kaya

I just installed Xolox 1.5 build 740. It searches
very slow and it is a memory Hog! I have 256 mb ram and when Xolox is runing my pc gets as low as 16 mb ram. Also every time I shut down Xolox I get an error message and this application error.

"Exception EAccessViolationin module XOLOX.EXE at
0004F417. Access violationat address 0044F417 in
module 'XOLOX.EXE' read of address FFFFFFFF."

__________________
Steve

Kaya:
I have to agree with the memory hog comment. It has locked my system up completely a couple times, with only the cursor and the hourglass still moving. I can't even bring up the system manager or task bar. Only way to get anywhere is to hit the power button and reboot. However, Xolox doesn't mysteriously disappear anymore. I also have been getting a 'connection' error message that asks me if I wish to reconfigure my settings. Build 740 is also slower than the original 1.5 release. That 1.5 release, except for the mysterious disappearance problem, really was a great leap forward. Xolox performed better, downloaded faster and found more hits than any previous version I've had (I've been using Xolox for about a year, now). I was really pleased until it started going AWOL on me. You were definetly heading in the right direction, sometimes there is a detour or two. I've got a 1.7G Athlon with 512Mb ram.

__________________
Wherever you go, there you are.

I can't say that I've run into the lockup problem, but I have a full gig of memory. It COULD be that Xolox uses a bit more memory during searches, and that 1 gig is enough for me not to run out of resources, or it may be debug code that's causing the bloat you are seeing. Yea, looking at the memory usage in Xolox, I see the mem usage going up a bit, currently at 50,440k of memory used by the process, no searches going, but a bunch of things in the queue to be downloaded. Slight memory leak is my guess.

Edit: A few hours later Xolox is at 177,072k mem usage, still with no searches. I do see that there are 3 leafs connected, so I'll see if that affects it or not.

So far so good. I've been running about four hours with this build and have not run into a shutdown yet. I'll leave it running overnight and report any problems.

Thanks for the quick turnaround.

Good news -- Xolox has run about 21 hours now with no silent disappearance. No way the last build would have done this!

Thanks

I thuink I figured out why Xolox is locking up my PC. There seems to be a max number of items one
can have in the down load que. Too many items
in the que causes my lockup problem.

I have not figured out what the max number is,
perhaps someone in xolox can look into this
and put a warning message in the next build.

__________________
Steve