If it's A new Morpheus on Gnucleus 1.7 code there will be no problem but if it's the 1.6 code... Ouch. You'd be screwed. |
corrupt files Some people were having problems with too many corrupt files using LW 2.4.0. The weird thing was that the corruption was happening after downloading just a few percent of the file. If you're having this problem and are willing to help debug it, please email me at crohrs at limewire dot com. dimagor, MooseMuffin, and treatid: I already sent you a personal message with some debugging instructions. If you have some time, any debugging information would be most useful. Thanks, Chris |
Startup is slow. Can this be improved? |
Startup probably can't be faster, because it's a Java Application. Java application load slowly, but run fast. |
Quote:
|
I encountered quite a decrease in download speed and got fewer hits when upgrading to 2.3.3. When I upgraded to 2.4.0, then 2.4.1, and also upgraded the Java engine to 1.4, things improved and it seems to me that my downloads is faster now. ;) Still, Limewire is trying to connect to 5-6 extra hosts now and then. The connection attempts disappear after a couple of seconds, but the established connections seems to be quite unstable, and they are renewing themselves after a while. Other than that, I'm quite happy with the improvements in the GUI using the 1.4 Java engine. (<Enter> now works on OK/Cancel dialogs - yeeah!) The number of hits on my searches has also somewhat decreased after upgrading to 2.4.x, but that may also be a bug in the Ultrapeer code - several of my connected Ultrapeers is 2.4.x. |
Quote:
|
Java/LimeWire using all processor Windows 2000, Java 1.4 on an AthlonXP 1500. From time to time, LimeWire/Java take up all my processor time (So much so that it nearly looks like the computer has locked up). If I have sufficient patience, processor usage drops back to a more reasonable level (usually between 10 and 20% use) after a half hour or so. I think that I have managed to close LimeWire during one of these peak usages - The Java VM continued to take up all my processing power (It is possible I just minimised LimeWire). This has happened on a few (perhaps as many as half a dozen) occasions now. I'm reasonably sure it isn't new to 2.4 of LimeWire. This could well be something like a garbage collection issue within Java and not LimeWire's problem. I think most of these near lockups have started when I've done a re-search - but I've done a lot of 're-search'es that have not caused any kind of lockup. Mark. |
For Mark Are you a leaf or ultrapeer? How many connections? Do you get this when disconnected from the network? |
I'm a leaf. 6 connections. While LimeWire/Java is taking all the processing time, LimeWire is unable to keep any connections for more than a brief period of time. Last time this happened (started a couple of hours ago) LimeWire claimed it was disconnected. Some uploads got a brief look in - downloads were not happening. Switching off the ADSL connection did not seem to improve (or worsen) matters. I got bored after a couple of hours of slowdown and killed Java from taskmanager. Restarting LimeWire went fine, picked up all the incompletes and is currently working without a problem. Mark This last episode started when I stopped LimeWire and restarted it because all the uploads had dropped to 0K - As LimeWire was going through restarting the (fairly larger number) of incomplete downloads it started taking all the processing time (I've set maximum number of downloads to 30). |
All times are GMT -7. The time now is 02:26 PM. |
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2024, vBulletin Solutions, Inc.
SEO by vBSEO 3.6.0 ©2011, Crawlability, Inc.
Copyright © 2020 Gnutella Forums.
All Rights Reserved.