Community
Participate
Working Groups
The dialog box that shows up when an OutOfMemoryError is thrown suggests for the user to increase the heap size using the -Xmx option. What it doesn't say is that "-vmargs" should be used! Some users don't initially tweak their eclipse installations, and this is likely to be the first error dialog that will force them to start tweaking command line switches. An unexperienced eclipse user will just pass the "-Xmx" to eclipse.exe, and since no error is reported, he will assume the option was accepted. (yes, I have just spent more than a day trying to help one of my users with an OutOfMemoryError, because he did follow the instructions!)
We should tidy this up for RC2
Here is a patch that mentions -vmargs Index: messages.properties =================================================================== RCS file: /home/eclipse/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/messages .properties,v retrieving revision 1.42 diff -u -r1.42 messages.properties --- messages.properties 26 May 2004 14:27:25 -0000 1.42 +++ messages.properties 31 May 2004 19:35:04 -0000 @@ -746,7 +746,7 @@ InternalErrorOneArg = An internal error has occurred.\n{0}\nSee the .log file for more details.\n\nDo you want to exit the workbench? FatalError_RecursiveError = A internal error occurred while showing an internal error. -FatalError_OutOfMemoryError = An out of memory error has occurred. You can prevent these errors in the future by increasing your heap size before you start the workbench using the -Xmx command line option. +FatalError_OutOfMemoryError = An out of memory error has occurred. You can prevent these errors in the future by increasing your heap size before you start the workbench using the -vmargs -Xmx command line option. FatalError_StackOverflowError = A stack overflow error has occurred. FatalError_VirtualMachineError = A virtual machine error has occurred. FatalError_SWTError = An SWT error has occurred.
Fixed in build 20040602
Thanks, Genady
Verified in 20040604
