LimeWire 4.3.3 Beta
 

The LimeWire 4.3.3 beta has been released. You can download the free version from the LimeWire download page . PRO users can download the beta from their personal download page.

LimeWire 4.3.3 include the following changes:
- Fixed widespread 'Could not move to Library' bug on Windows.
- Fixed 'Direct Connect' tab to update your IP address as it changes, as well as show that you are behind a firewall or router if LimeWire detects it.
- Added a 'Shutting Down LimeWire...' window as LimeWire closes.
- Fixed internal bugs in UPnP.
- Optimized filtering based on IP addresses. Thanks to Philippe Verdy for this optimization.
- Reduced the upload bandwidth required when downloading files via LimeWire's new "firewall to firewall" technology.
- Added the Java version to the 'About' dialog.
- Added a Creative Commons playlist when in LimeWire's shared playlists (using DAAP). Thanks to Roger Kapsi for contributing this.
- Fixed improper window sizing after changing themes or restoring from the system tray when using Java 1.5.
- Simplified firewall configuration and added UPnP configuration. This is under your Options (or Preferences on OSX), Advanced -> Firewall Config.

Barring any terrible bugs, this release will go into production on Monday.

Thanks,
The LimeWire Team

Yup. :)

Thanks for the direct connect improvements and the firewall config. I really appreciate them! I'll stress 4.3.3 as UP this weekend.

Merci beaucoup à tous ceux qui participent au développement de LW :)

Connected as an UP here (outgoing connections only), even though I'd forgotten to turn off my firewall.

Quote:

LimeWire version 4.3.3 Pro Java version 1.4.2_05 from Apple Computer, Inc. Mac OS X v. 10.3.7 on ppc Free/total memory: 3972384/19726336 -- listing session information -- Current thread: AWT-EventQueue-0 Active Threads: 70 Uptime: 4:28 Is Connected: true Number of Ultrapeer -> Ultrapeer Connections: 25 Number of Ultrapeer -> Leaf Connections: 0 Number of Leaf -> Ultrapeer Connections: 0 Number of Old Connections: 0 Acting as Ultrapeer: true Acting as Shielded Leaf: false Number of Active Uploads: 0 Number of Queued Uploads: 0 Number of Active Managed Downloads: 0 Number of Active HTTP Downloaders: 0 Number of Waiting Downloads: 0 Received incoming this session: false Number of Shared Files: 349 Guess Capable: true Received Solicited UDP: true SIMPP version: 7 Port Stable: true FWT Capable: true Last Reported Port: 20300 External Port: 20300 IP Pongs Received: 0

And congrats aussi on all the developments.

That's normal behaviour. LimeWire doesn't expect people to be consistently changing their firewall status, and will remember whether or not you received a connection during your last run. If you did, then LimeWire has a chance of starting up as an Ultrapeer on the next run. Of course, if during that run it can't get any incoming connections, the next run won't start as an Ultrapeer.

Thanks for the quick reply Sam

hmmm--makes sense, but why not throw up the "detected a firewall warning" then as a reminder?

(btw--I rarely change the firewall setting on the desktop computer, but the laptop firewall changes daily between work and home. I'd guess other laptop users might be in the same situation).

Having a dynamic IP I've noticed two problems related to IP changes in a same session of LW:

1) On downloads, LW doesn't detect that IP have changed and shows a download speed of 0KB/s for a long time before going into "more sources need" (when there is no download mesh or a little dl mesh)
-LW should detect the IP change, time out those connections and request again download ranges from the previous uploading hosts.

2) On uploads, clients loose the source of the files they were dling
-LW should send a queryhit to those IP so they can continue dling from the new IP without them making a new search in the case the download mesh is inexistent.

Ciao

FWIW, in 4.3.3 VM rose overnight @ 5.7 KB/second on OS X here (no searches or downloads; few uploads; running as an UP. details available).

Thread count looked OK (~150), but CPU % seems high at ~ 40-50%

Been running new version for about 3 hours now. No problems yet, and the new version got rid of it appearing to go into standby mood. I am just a little confused why it keeps shifting between excellent and turbocharged, and in connections I show incoming and outgoing as UP this has never happened before.
Not to bright on software sometimes. But I sure do like the way it operates. Running windowsXP MCE sp2 512MB DDR2@533Mhz 1.5MB/s connection