|
| |||||||
| Register | FAQ | The Twelve Commandments | Members List | Calendar | Arcade | Find the Best VPN | Today's Posts | Search |
| | LinkBack | Thread Tools | Display Modes |
| |
October 21st, 2005
| |||
| |||
 By default LimeWire tells the Java virtual machine limits itself to 128 MB of heap size. It doesn't matter that you have 2 GB of RAM. Note that the JVM also uses some RAM for JIT-compiled methods, thread stacks, native library code, etc., so the JVM may use a little more than 128 MB total, but the heap will be limited to 128 MB. Which platform are you running? The way to change the parameters passed to the JVM is platform specific. Which OS are you using? |
| |
Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| java.lang.OutOfMemoryError: unable to create new native thread | dlangdaman | Download/Upload Problems | 8 | June 17th, 2009 09:25 PM |
| java.lang.outofmemoryerror | castalia | Download/Upload Problems | 0 | February 12th, 2007 10:42 AM |
| Limewire - "java.lang.outofmemoryerror" - "no stack trace available" | Bourbon | General Windows Support | 1 | November 9th, 2004 07:23 AM |
| java.lang.OutOfMemoryError in phex 0.74 | Unregistered | General Discussion | 4 | August 14th, 2002 09:38 AM |
Hybrid Mode
