Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 85771

Summary: Export Jar fails with Internal Error 3.1M4 Out of Memory
Product: [Eclipse Project] JDT Reporter: Paul Lever <paull>
Component: UIAssignee: JDT-UI-Inbox <jdt-ui-inbox>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: P3    
Version: 3.1   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Paul Lever CLA 2005-02-17 17:55:07 EST
I was moving code over from 3.0 to 3.1 M4. I run Export... on a pacakge, it rn
sthrough the Wizard, does a bunch of exporting and then finishes with an
Internal Error. It ends in Out of memory. Don't know if this is really just a
simple out of memory or something wrong with the exporting. It works fine on the
same machine on 3.0 
Error log info is below:
Error Feb 17, 2005 14:16:12.144 Internal Error
java.lang.reflect.InvocationTargetException
	at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:303)
	at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:824)
	at
org.eclipse.jdt.internal.ui.jarpackager.JarPackageWizard.executeExportOperation(JarPackageWizard.java:173)
	at
org.eclipse.jdt.internal.ui.jarpackager.JarPackageWizard.performFinish(JarPackageWizard.java:147)
	at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:670)
	at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:342)
	at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:543)
	at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:833)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2803)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2448)
	at org.eclipse.jface.window.Window.runEventLoop(Window.java:718)
	at org.eclipse.jface.window.Window.open(Window.java:696)
	at org.eclipse.ui.actions.ExportResourcesAction.run(ExportResourcesAction.java:166)
	at
org.eclipse.ui.actions.BaseSelectionListenerAction.runWithEvent(BaseSelectionListenerAction.java:167)
	at
org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:555)
	at
org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:505)
	at
org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:419)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:833)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2803)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2448)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1569)
	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1540)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:285)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:144)
	at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:102)
	at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:220)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:273)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:129)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.eclipse.core.launcher.Main.basicRun(Main.java:185)
	at org.eclipse.core.launcher.Main.run(Main.java:710)
	at org.eclipse.core.launcher.Main.main(Main.java:694)
Caused by: java.lang.OutOfMemoryError
Comment 1 Paul Lever CLA 2005-02-17 23:46:24 EST
Problem goes away when I add to the Eclipse command line:
-vmargs -Xms64M -Xmx512M

So I guess it really was running out of memory. It would be nice if the error
message was something cleaner than Internal Error, other than that you can close
this.
Thanks
Paul
(In reply to comment #0)
> I was moving code over from 3.0 to 3.1 M4. I run Export... on a pacakge, it rn
> sthrough the Wizard, does a bunch of exporting and then finishes with an
> Internal Error. It ends in Out of memory. Don't know if this is really just a
> simple out of memory or something wrong with the exporting. It works fine on the
> same machine on 3.0 
> Error log info is below:
Comment 2 Martin Aeschlimann CLA 2005-02-18 09:06:40 EST
The memory issue is know. For the error dialog, file a request against platform UI.

*** This bug has been marked as a duplicate of 82804 ***