Frostwire crashes - too many shared files??
 

Thanks to a small contribution from a friend, the number of files that I am sharing has tipped over 20,000 files (yes, they are music files. Yes, it takes up over 100Gb of data).

Problem is, neither LimeWire nor FrostWire is able to finish indexing these files. They both crash about 2-4 hours into it, and become completely nonresponsive.

Is this a limitation of LimeWire/FrostWire/Java?

Possibly, I've never heard of any gnutella program sharing much over 10,000 files. It's more likely a limitation of Java. If you want to 'try' to share that many files, add them to FW or LW bit by bit so they don't have to hash them all at once. So add 500 or 1,000 or less per occasion. Then add more later, bit by bit if possible. IMHO You might still have problems but it's the way I'd approach it. After all, it's the initial adding them to shares for the 1st time when they are hashed. AFAIK Something else you could do is, not try to connect to the network whilst you're adding the files/whilst the files are hashing. BTW unless I'm mistaken, I think I came across someone who was sharing 16 k files

Re: Frostwire crashes - too many shared files??
 

It is a limitation. AFAIK, the limit is ~14,000 files. I can explain why, but my back is sore from sitting at my desk. There is a patch to share over 100k files. But it requires alot of RAM and increasing the JVM memory allocation.

Well, I am planning on upping my system to 2Gb of memory (which is expensive, since I run an Opteron and need ECC Registered PC3200), so perhaps this patch is for me. Do you happen to have a link handy for me?

Also, I have both 32-bit and 64-bit implementations of Java installed (I have WinXP x64 Pro). I'm not sure how to force FrostWire to preferentially use the 64-bit implementation of Java.

TIA