im on winXP sp2 and it seems to eat as much ram as i have (512) cpu usage is still pretty high too (2.1GHz)

all when downloading, or sharing a large library (i have 3300+ files)

Humm, right now the RAM is at 170MB. I can say that LW started using 67MB ram, then with downloads the amount of useage grew up to 105 MB, while downloading much more than 40 MB. I left LW overnight without downloading but uploading and the ram useage is now 170 MB. Usually I leave LW uploading but not dling for days and this is my observation: without dling, LW can stay low in ram useage, but as soon as you dl something this seems to trigger a memory leak that persists even when downloads are done.


Ciao

1. Even with the same file name LimeWire will not ask to overwrite a file if the file does not match case.

2. The Column positions are not saved to the last place it was moved.

3. Seems that alot of files tend to corrupt when heavily downloading. (This could be the servents fault? I dont know.)

4. Overall program repainting seems to be slow at times.

5. The library does not show subfolder contents under saved files.

Thanks a lot ultracross, I may not be able to look into them as soon as I would like, but those files will definitely help us track down what's happening.

Keep up the good work, you guys are the best beta testing community we've seen. Without you LimeWire would be a lot buggier (and we've done our part (unintentionally) making it buggy, believe me ;) )

I can confirm that the mem leak happens when and continue AFTER downloads are made. When I finished dls, LW was using 100 megs, a day after it was using 220MB only uploading. I started LW again and after 24 hour, the mem usage is still at 80MB. Of course this is on osx.... with all Apple VMs problems.

Ciao

Salut et voilà

I've been trying to confirm, but it's not happening with Jaguar and my G3. The resident memory goes up for a bit, but then is recovered.

Salut Stief, maybe it is specific to java 1.4.2 on Tiger 10.4. I know Apple modified the JVM for Tiger over Panther.... Didn't try 1.5. I'm beginning to think Sun should do the Java for Macs too. I wonder what the apple java folks are doing :rolleyes:

Great :rolleyes: Apple seems to fix the Vmem problem on Tiger, then gives you a real memory problem.

As for what Apple is doing--not much that I can see. I browse http://lists.apple.com/archives/java-dev/2005 almost daily, and "memory" just doesn't seem to be on their radar.

Sigh.

Anyway, I'll keep watching the memory use charts (I try to save them after each session).

I also noticed something like this, limewire sometimes does not switch from a manilla folder to a green check mark after completeing the download.

-- listing session information --
Current thread: AWT-EventQueue-0
Active Threads: 24
Uptime: 0:57
Is Connected: true
Number of Ultrapeer -> Ultrapeer Connections: 0
Number of Ultrapeer -> Leaf Connections: 0
Number of Leaf -> Ultrapeer Connections: 7
Number of Old Connections: 0
Acting as Ultrapeer: false
Acting as Shielded Leaf: true
Number of Active Uploads: 7
Number of Queued Uploads: 0
Number of Active Managed Downloads: 0
Number of Active HTTP Downloaders: 0
Number of Waiting Downloads: 40
Received incoming this session: true
Number of Shared Files: 4148
Guess Capable: true
Received Solicited UDP: true
SIMPP version: 7
Port Stable: true
FWT Capable: true
Last Reported Port: 6346
External Port: 6346
IP Pongs Received: 0


Its been happening quite frequently upon limewire startup that i will get 7 ultrapeer connections, and then as time goes on, it comes back down to 5. does this have anything to do with how many files i share? or is this not supposed to happen?