i wish i knew what your talkin about
 

hey guys, do you know of a website that would break down and explain this java stuff you're talking about here? im hoping i can find some understanding despite not being a developer.

Hi EllisD--welcome to the wonderful world where users like me who know nothing about java bug the developers and opensource coders who do :p

btw--message me and I'll send you my daily reading list.

@Sam--here's more about the Virtual Memory problem with OSX

busy host, need more sources, and resume trigger the rise.

--it's not jum-specific (used et voilà's CVS build and Roger worked me through building one myself). With both I was able to start and stop VM growth.

--the garbage collector fix doesn't help with downloads. Jens is looking into it further.

this is with a CVS version built this AM EST Nov 8, on a G3 running OS 10.3.6 with all view options off, running as an UP and uploading 2 GB over 8 hrs.

More detailed info is on my iDisk (stief11@mac.com; no password) help yourselves

Browse host spikes
 

(Not sure if this belongs here or in the 4.1.9 thread)
Finally found the cause of the strange spikes in the upload bandwidth window: they happen when someone browses me. Saw this when jum tried, then confirmed by et voilà.
btw, the stats are from the end of the session posted above.

The last 24 hrs had LW 4.1.8 running, dwnlding & uplding non-stop unattended with (Stief's advice:) Library & Connections windows hidden, & (et voilà's advice:) with the probram hidden; total ram use was 100 MB, & VM 550 MB. As soon as I brought the program out front again, ram seemed d to increase at the old rate. But hidden again & it seems to stem/limit this increase. Hiding it certainly makes the ram jump back a few mb.
This is the best result I've been able to get running LW for such a period.

LODR you bring a good point! I always (when not searching or checking uploads) hide LW. My CVS build running since 94 hours (!) is using 77,60 MB RAM and 700 MB virtual memory.

Ciao

4.19 is no better than 4.18 which is no better than ....
 

any of the versions since 3.6.15 which simply refuse to launch without an immediate crash on startup.

You guys at Limewire have yet to figure out what is making this happen consistently. Read the forums, you will see that I am not alone.

dbdurham --

We'd like to fix it, but are unable to unless you can provide some details about your computer. Important things include your operating system, your java version, what specifically you mean by "crash", etc.