Bug 23677

Summary: java.lang.OutOfMemoryError when setting class path
Product: [Eclipse Project] JDT Reporter: Gary Gregory <ggregory>
Component: CoreAssignee: Philipe Mulet <philippe_mulet>
Status: RESOLVED WORKSFORME QA Contact:
Severity: normal    
Priority: P3    
Version: 2.0.1   
Target Milestone: 2.1 M2   
Hardware: PC   
OS: Windows 2000   
Whiteboard:

Description Gary Gregory CLA 2002-09-17 19:57:43 EDT
I changed my class path to updgrade from JUnit 3.7 to 3.8.1 and got the error 
below. I had been running e for a couple of days, while it was slow yesterday 
and used up about 119MB of RAM, today it is faster and is now using 111MB of 
RAM. My box has 512MB, the task manager shows 436MB used. I start e as follows:

C:\eclipse-R2.0.1\eclipse.exe --vm c:\java\j2sdk1.4.0_01\bin\javaw.exe -
data "C:\Documents and Settings\ggregory.PC1073\My 
Documents\eclipse\workspaces" vmargs -Xmx256m

Now, I click OK again to apply my path settings, the output folder gets srubbed 
again and the world gets recompiled without errors.

!ENTRY org.eclipse.jdt.ui 4 1 Sep 17, 2002 17:04:34.709
!MESSAGE Internal Error
!STACK 0
java.lang.reflect.InvocationTargetException
	at org.eclipse.jface.operation.ModalContext.runInCurrentThread
(ModalContext.java:312)
	at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:249)
	at org.eclipse.jface.dialogs.ProgressMonitorDialog.run
(ProgressMonitorDialog.java:376)
	at 
org.eclipse.jdt.internal.ui.preferences.BuildPathsPropertyPage.performOk
(BuildPathsPropertyPage.java:140)
	at org.eclipse.jface.preference.PreferenceDialog.okPressed
(PreferenceDialog.java:577)
	at org.eclipse.jface.preference.PreferenceDialog.buttonPressed
(PreferenceDialog.java:175)
	at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:398)
	at org.eclipse.swt.widgets.TypedListener.handleEvent
(TypedListener.java:87)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:77)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:827)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:1529)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1291)
	at org.eclipse.jface.window.Window.runEventLoop(Window.java:562)
	at org.eclipse.jface.window.Window.open(Window.java:542)
	at org.eclipse.ui.dialogs.PropertyDialogAction.run
(PropertyDialogAction.java:159)
	at org.eclipse.jface.action.Action.runWithEvent(Action.java:749)
	at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection
(ActionContributionItem.java:407)
	at org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent
(ActionContributionItem.java:361)
	at org.eclipse.jface.action.ActionContributionItem.access$0
(ActionContributionItem.java:352)
	at 
org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent
(ActionContributionItem.java:47)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:77)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:827)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:1529)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1291)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1256)
	at org.eclipse.ui.internal.Workbench.run(Workbench.java:1239)
	at org.eclipse.core.internal.boot.InternalBootLoader.run
(InternalBootLoader.java:775)
	at org.eclipse.core.boot.BootLoader.run(BootLoader.java:462)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:324)
	at org.eclipse.core.launcher.Main.basicRun(Main.java:247)
	at org.eclipse.core.launcher.Main.run(Main.java:703)
	at org.eclipse.core.launcher.Main.main(Main.java:539)
Caused by: java.lang.OutOfMemoryError
Comment 1 Olivier Thomann CLA 2002-09-20 08:48:09 EDT
In your command line, you should put -vmargs instead of vmargs. Then the heap
size will really be bigger and you should not get an OutOfMemoryError anymore.
Please add a note if this fixes your problem.
Comment 2 Gary Gregory CLA 2002-09-27 13:24:08 EDT
So far so good. Thank you.
Comment 3 Philipe Mulet CLA 2002-10-02 06:46:17 EDT
Closing.
Comment 4 Philipe Mulet CLA 2002-10-02 06:48:31 EDT
Closing