The incomplete icon showing may be a bug, we'll check that out. The sizes not matching up was probably just a repainting issue, in that the size column didn't fully repaint.

Sweeeeeeeet. That's it. I'm taking the plunge. Limewire Pro here I come!!

re icon paintings, if a file is downloaded from a browsed host, discovered through a "What's New" search, the file icon may not update in both seach tabs. This seems to happen when the search result panel was scrolled past the download entry.

Also, scrolling through long lists of a browsed host's files and randomly selecting one or two files from each screenful also seems to be a problem for keeping the icons updated.

speaking of long lists of browsed hosts--they don't seem to be causing the gui locks I saw before. Coincidence? or was that problem fixed too?

for the record, Apple's java in 10.3.9 still runs up the VMem. If I make sure there are no downloads or incomplete files, I can usually flatten the rise and let LW run all night without risking major problems in the morning. (graphs available). I've seen almost no discussion of it on the Apple java dev lists, but I'm losing confidence it is even on their radar any more. I'm beginning to think it's just my set-up.

On the bright side, running as an UP with no downloads keep the thread count at about 30, and the G3 CPU at 20%. So the optimizations have really opened the door for much greater longer uptimes here--thanks.

The bad side is that the downloads are getting easier and quicker, so I'm checking out larger files than before. This means I'll have to get a larger laptop to share the goodies.

Is there a 3 bug limit on sending or triggering the bug reports? The console shows 4 of the "java.lang.Error: java.net.SocketException: Connection reset by peer" entries, but only the first three popped up the Review dialog this session (options set to always review).

Yesterday's session was set to "always send", but only three with my client id showed in the bugreports page when I checked today. Console, however, logged over 40 of them.

Sheesh. It's been many months since I've seen those lousy results sent by "GNUC," but now they're baaack. I kicked the one GNUC from connections, but that didn't help

Has something changed to allow those results in again, or was it just my luck to link to some bad vendors?

I've had lousy luck searching for rarer content these past weeks, so I'm beginning to wonder if the code changed to prefer more popular content. (Hope it's not the network getting flooded with spam searches). For now I'll be optimistic that it's the almost two million users that's increased the horizon beyond my reach.

btw--I'm not interested in boxing. cf http://www.gnutellaforums.com/showth...470#post141470

Attached Images

gnuc garbage.png (39.8 KB, 5013 views)

Rare content is of course a problem on gnutella. Try disabling ultapeer mode. Leaves have by far the larger search horizon.

As for the GNUC client, I see those every now and then but not consistently.

Yup, there's a three bug limit in a few places. There's a limit for showing the review dialogs (so they don't keep stacking up forever), and there's a limit on the server side. Once it sees three of any given bug, it tells people to stop sending that particular bug again for quite a while. This prevents occasional situations on one computer from causing huge spikes in reported bugs. So long as the problem is widespread, we'll see lots of reports from different computers.

How are the bugs sent exactly, is it like a magnet link or something. Not that it's important to know just curious.

By clicking 'send' when an Internal Error pops up in the client.

No I meant after you send a report, how is it transfered to LW.