4.9.29 Pro is having a little problem I am port forward no firewall icon showing all things working good except it doesn't want to connect to more than 4 leafs. UP is not disabled but for some reason does no want to connect as a UP.

Attached Images

cropimage.jpg (74.6 KB, 48 views)

__________________










A little common sense goes a long way

Later Grandpa

Hmm--here 4.9.29 is connecting much more easily as an UP, and seems to pick up leafs much faster than the previous version. I was about to ask if this is coincidence.

Oh well.

--some other notes:

-browse host needs a "refresh" option (one that won't dismiss the tab if the host happens to be busy when the "repeat" option is used).

--Bearshare handles busy queues really well: overnight downloads moved from busy, to queued, to complete very well. Before, I'd avoid BShare results.

4.9.29 is even more of a bee with an itch with Apple's VMem on java 1.4.2_05 too. It quickly gets up well over a gig, and thus I can't run it for more than dozen hours without it crippling my machine [soon to be replaced accordingly].

Under low HD conditions, any dialog that LW needs (like the delete confirmation, or the low HD warning), hangs LW for more than 5 mins. I presume the dialog was cached in the VMem, and takes forever to be recalled.

Although this doesn't affect most of the UP connections, the hang seems to trigger the loss of most of the leafs.

btw--if anyone want to see how many LW cabo versions are out there--download a large japanese movie. Within minutes my upload queue maxed out (20 throttled to 90KB/s) and worked smoothly for about an hour. The bandwidth controls handled the load very well, both up and down, and didn't interfere with other browsing and net activities. Leafs and peers didn't seem affected either. Other than the HD working pretty hard, I couldn't tell LW was working so busily. Nice work on all the core features that are needed to make that happen

It can't seem to make up it's mind how many connections it wants. It did finally make the 5th connection some time during the night. I did finally get a UP connection this morning and it took about 15 min. to get to 30 peers but once it got there it stayed between 29 and 31 while searching and DL.

I got virtually the same results in UP and Leaf mode both good search and DL. While DL 20 consecutive files at a time 650Kb+ all files completed the resume feature appears to work well. No corrupt file messages.

This latest round of testing was done on a fresh reformat. Got a virus so I reformatted and re installed. (Win:32 Trojano-324) more on that in a latter post. But I figured since all was new I just as well try to reproduce some of the problems other are having.

When I first started running LimeWire I was using Windows firewall. With firewall properly configured LW detected a firewall when it should not have. No matter how I configured the firewall or what mode I ran in. IE manual port forward or UPnP. When I installed Norton Internet security and disabled windows firewall it no longer detected a firewall. It would not connect as a UP with windows firewall. I had a couple of install problems but they were not the fault of LW will elaborate on that latter.

Any way 4.9.29 seems to be working very well other than it can't decide how many connections it wants. I did not see the high memory usage that stief saw but I did not run in UP very long about a hour of heavy testing memory usage got to 75MB.

The screen shot below was taken a hour ago connections still the same so at this time I do not know if it will drop to 5 or not. Also I should add that I ran in leaf mode all night DL 0 / UL 5 at 45KB LW did go into sleep mode kept 1 connection and it did not have the disconnect message. When I woke it up it immediately went to 5 connections.

Attached Images

#2.jpg (79.8 KB, 34 views)

__________________










A little common sense goes a long way

Later Grandpa

4.9.29 fixes a serious bug which was causing nodes to think they were firewalled when they actually weren't. However, many ultrapeers will need to upgrade before the full effects of the fix can be felt.

__________________
The more you debug it, the more it bugs

zab

I should have been a little clearer LimeWire worked fine with other Firewalls IE it did not detect as being firewalled and had no problem connecting as a UP. I found that LW preformed better for me as a UP than it has ever before with any previous version. LW is having a problem with the Windows firewall though. Unfortunately I do not know much about programing and can not give any clues as to why. I just know as a end user it is.

And by the way Congratulation 4.9.29 seems to be very stable in the connection department I had no problems at all with disconnects. And for some reason there is an improvement in the share department more of my files in my share folder appear to be available to others than in previous versions. I do not no if it was a intentional fix or accidental but Thanks.

__________________










A little common sense goes a long way

Later Grandpa