As with the previous versions, build 388 drives me crazy because it only lasts about 20 - 30 minutes before it crashes with the same "out of resources" message. I am using it on W2K, 750Mhz pentium with 256MB ram and nothing else running. The last response I had to my entry in the "Bug" forum was that this message is due to servers disconnecting or something.

Does this happen to everybody ? I mean I have been using this for about 3 weeks and it never changes. Surely this can't be standard behavior for the tool.

The only thing unusual about my case may be that I have about 1000 songs queued up for download. Is there ANYTHING that can be done ?? I'm getting incredibly frustrated ;-)

Please help before I go ove the deep end

No this does not happen to everybody. As I remember I tried to point out when Xolox uses the most of you computer's resources. In that way, if your computer was exaggerating Xolox's normal resource usage, that would be the most likely time that your computer would have problems. When Xolox is trying to connect to new hosts many users may notice a slow down in their system. Additionally, because of intigral problems in Windows, such as memory leaks, if you computer has been running constantly for a while (depends on the machine) your computer may stop responding until Xolox connects (which in that case takes longer). Try rebooting once in a while if you do not do so very often.

Thanks.

Actually, even when I do reboot, it does not help much. At best, it might let Xolox run for 40 minutes before I get the "out of resources" error message and Xolox closes itself. Do you have any idea which resources it might be referring to ?

I still think there is a different problem than memory leaks. I have let lots of other programs run around the clock, including Bearahre, napster, etc and have never had this problem with any of the others.

So, I don't think it is a system issue, I think it must be something specific to Xolox. Can you learn anything from the rror reports it generates and sends to you ?

Xolox is sensitive to memory leaks and other resource allocation problems. (this is especially apparent in WinME) Win2000 usually does not have much of a problem though. It also may be a result of the combination of programs being run. (not all programs play nice together) It helps if you have all you your service packs too.

Thanks for the tip.

I have all of the service packs installed and no other apps running.

Shilene, you said the problem yourself:
"The only thing unusual about my case may be that I have about 1000 songs queued up for download. "

Want to try and canceling about 950 of those? Maybe it would help don't you think ? :P

And you wonder why you get an our of resources error?
good luck

Btw, this is being moved the the proper section in this case, support: general/bugs.

If 1000 songs queued is too many then what is the maximum that should be used ? How many is too many ?

Is there a way to save off a bunch of the queued songs or would I need to search and add them again later ?

If I pause most of the downloads, would that relieve the resource problem ?

Pausing should help. Then Xolox is noy spending time trying to download them. However, if you really have alot of songs waiting to download, you have to think of the space in memory each of those takes up. (there is alot of information stored besides the name of the file)

I had no idea you really had near 1000 songs waiting. (assumed it was more like 20, I have noticed poeple tend to exaggerate those things) The number you can have at the same time is really best determined by exparementing with it. (everyone's computer is different)