javaw memory usage
 

i know swing generally sucks. i was just wondering if any else finds that javaw takes up 75 mb of mem (!) for limewire.

its a great program by the way, keep up the good work

Yes, after running the program for 24+ hrs, it will take up 80mb of ram and use 1/3 of the processor time.

If this were fixed, I could let limewire run all the time, thus improving the network.

I run windows 2000

Buck

lol, mine immediately takes up 95 megs!! I thought www.edonkey2000.com (better for big files!!!!!!!!!) took up a lot (15 - 30 megs) but this is INSANE!! I do have 512 megs, but 95 megs for a simple sharing program?? Most GAMES don't even use that!!!!!

WINDOWS XP
 

I downloaded another java runtime package from www.sun.com which was made specifically for XP... This fixed a lot of memory problems, it is stable at 38 megs right now... Better than it was ;)

We're working on this issue right now -- there appears to be a memory problem sometimes when you become an UltraPeer. Any more details people can provide as to exactly when you are seeing this behavior would be helpful. Can you definitely not replicate it with the JRE for XP? I only ask because it appears to only happen some of the time on the normal 1.3.1 JRE, and only if you become an UltraPeer with many client connections.

Is anyone experiencing memory issues when you are not an UltraPeer (do not have a lot of client connections listed in your Connections tab, and with your status appearing as "UltraPeer" in the lower left)?

Thanks.

Are you having memory problems with LW 1.9? We're still trying to iron the last few kinks before the official public, non-beta release.

If you're having problems with LW 1.8x or earlier, try changing your desktop shortcut to something like the following

D:\Program Files\JavaSoft\JRE\1.3.1\bin\javaw.exe"
-ms4m -Xminf0.10 -Xmaxf0.25 -jar RunLime.jar

replacing "D:\..." with the path to your version of java. Note this shortcut is exactly like the old shortcut except for the -ms/-Xminf/-Xmaxf options. Those will hopefully keep Java from growing the heap too much.

Hi everyone!

I'm using Windows XP Home Edition. I used the Windows Task Manager (CTRL+ALT+DEL) to see how much memory the process javaw.exe used. It said 24 MBs, but looking at the amounts other people are posting, that just doesn't sound right. At the time I checked it, LimeWire was in UltraPeer mode and had been running for 45 minutes. It had 3 connections for a total of about 250 hosts.

Is there a better way to find out how much memory LimeWire (or any other program) is using?

Other info: PIII 866, 448 MB RAM, LW 1.9beta, 56k connection

TruStar-

The Task Manager works well for this. The only question I have is were you definitely in UltraPeer mode (it said UltraPeer to the lower left of the connections tab)?

This would be a serious bug, as users connected via modem should never become UltraPeers, as they could potentially get hammered by the messaging.

Thanks.

Yes, it says UltraPeer on the Connections tab, and I have the LW option set to "modem". However, I did not disable the UltraPeer feature in the options window. It switches once in a while, but I am finding that most of the time, it is in UltraPeer mode.

I just double-checked everything again, and I am getting the same readings, except that the mem usage is slightly lower at only 24 MBs.

Using an upload / download meter, I see that my uploads and downloads bandwidth usage is fairly high (I mean when only LimeWire is running). I average about 4 k upload and 2 k download. No other transfers (including LW file uploads) were occurring at the time I recorded these stats.

Maybe you should wait before you release the official version of 1.9?
:-|

Yeah, we're definitely waiting until we fix some of the pending issues, especially the memory problem. The label to the lower left means that we are considering you UltraPeer -- capable (which we should not be), but do you ever actually become an UltraPeer (i.e. do you ever actually see connections to yourself that are labelled as "client")?

Thanks again.