[YoThisBling]

Has anyone noticed that if you search for something and you get over 100,000 sources after hitting the get more results button, LimeWire will end up having an internal error and max out your cpu usage to a 100? This happens all the time to me. I am using 4.12.6 and this has always happened in the previous versions since the release of the get more results button!

[Sam]

Do you mean 100,000 search results in a single tab, or 100,000 sources for a single download?

[YoThisBling]

Originally Posted by Sam

Do you mean 100,000 search results in a single tab, or 100,000 sources for a single download?

100,000 Search results, sorry about that.

[hopalong]

This internal error problem exists here too, when i browse one or more users and the number of files in the search tabs is greater than about 20-25 thousand. As the number increases getting the results, LW uses more and more processor time, up to 95-100 % and at the end comes the internal error. If i try to recover i get more internal errors.
Sometimes LW can continue, i can shutdown it, but the downloads.dat/bak is empty already.
That's why i maintain 10 copies of these 2 files periodically (but sometime forget to make a copy).
The de-celeration is already sensible about 3 thousand files. I saw this in other java based client too.

[Sam]

We'll try to reproduce and fix it. Sorry 'bout that.

[hopalong]

i hope you'll find it.