Community
Participate
Working Groups
Suns jvm has afaik a default max heap size of 64MB. This is very, very small. In the newsgroup its a faq how to solve OutOfMemoryException. So it would be good to assume a sun jvm is used and to append a -Xmx128M to the -vmargs section.
I am still concenern about why the VM and Memory usage goes above the value I set on -Xmx In my case I set it to -Xmx96 but I see the VM Size column reaching 128MB and the Memory Used column just slightly lower than that. It may be because of plug-ins and not eclipse itself. Perhaps if eclipse had a plug-in or something like a memory profiler for plug-in memory usage.
In general the launcher should just run the VM. All VMs are differnet and all situations are different. With the advent of Eclipse as an RCP, there are many scenarios where larger memory sizes are not warranted. closing.
Number one scenario for eclipse is still the java ide. For the normal user it will look like a fault of eclipse if the jvm dies with OOME. Most users are running eclipse on top of sun jvm on windows. RCP developers can easily change the soucres to whatever they like. Or setup an own installation routine. So sad to see this bug closing. Hopefully with 1.5 with its "Java Heap Self Tuning" more users will never see OOMEs during their evaluation.
Please reconsider this for 3.0. I understand the reasons for wanting to be JVM independent but this is one of the top problems new users run into where I work so it would be good to address it somehow. Maybe there's another way to solve it, perhaps something like that workspace selection dialog (or even a field inside that existing dialog)? BTW I fear even 128M may be too small. In 3.0 I have to use 300M (recently increased from 256M) for a workspace containing binary projects for the Eclipse IDE itself. JDK1.4.2_04, 3.0M9.
In response to Comment #1: Heap size (which is what is specified by the -Xms and -Xmx options) is only one component of total memory usage. There are lots of other things that make up the total memory usage. Plus, the Windoze task manager is not always accurate in reporting actual memory usage by a process, and Windoze in general is not as good at process memory management as it could be.
*** Bug 66341 has been marked as a duplicate of this bug. ***
