Bug 23769 - java.lang.OutOfMemoryError
Summary: java.lang.OutOfMemoryError
Status: RESOLVED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0.1   Edit
Hardware: PC Windows 2000
: P3 critical (vote)
Target Milestone: 2.1 M2   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 25936 (view as bug list)
Depends on:
Blocks:
 
Reported: 2002-09-18 15:18 EDT by ram2108 CLA
Modified: 2002-11-11 10:38 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ram2108 CLA 2002-09-18 15:18:50 EDT
When i am creating a new project with existing file system.I am getting Out Of 
Memory exception.I didn't have this problem with releases before v2.
I am attaching the extract from log. 

SESSION Sep 18, 2002 14:13:11.498 ---------------------------------------------
java.version=1.3.1_02
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86 -install 
file:C:/eclipse/eclipse/
!ENTRY org.eclipse.ui 4 4 Sep 18, 2002 14:13:11.498
!MESSAGE Unhandled exception caught in event loop.
!ENTRY org.eclipse.ui 4 0 Sep 18, 2002 14:13:11.498
!MESSAGE Failed to execute runnable (java.lang.OutOfMemoryError)
!STACK 0
org.eclipse.swt.SWTException: Failed to execute runnable 
(java.lang.OutOfMemoryError)
	at org.eclipse.swt.SWT.error(SWT.java:2119)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages
(Synchronizer.java:98)
	at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:1506)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1294)
	at org.eclipse.jface.operation.ModalContext$ModalContextThread.block
(ModalContext.java:133)
	at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:258)
	at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:720)
	at 
org.eclipse.ui.wizards.datatransfer.WizardFileSystemResourceImportPage1.executeI
mportOperation(WizardFileSystemResourceImportPage1.java:375)
	at 
org.eclipse.ui.wizards.datatransfer.WizardFileSystemResourceImportPage1.importRe
sources(WizardFileSystemResourceImportPage1.java:582)
	at 
org.eclipse.ui.wizards.datatransfer.WizardFileSystemResourceImportPage1.finish
(WizardFileSystemResourceImportPage1.java:415)
	at 
org.eclipse.ui.wizards.datatransfer.FileSystemImportWizard.performFinish
(FileSystemImportWizard.java:97)
	at org.eclipse.jface.wizard.WizardDialog.finishPressed
(WizardDialog.java:577)
	at org.eclipse.jface.wizard.WizardDialog.buttonPressed
(WizardDialog.java:312)
	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.actions.ImportResourcesAction.run
(ImportResourcesAction.java:87)
	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 java.lang.reflect.Method.invoke(Native Method)
	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)
!ENTRY org.eclipse.ui 4 4 Sep 18, 2002 14:13:11.514
!MESSAGE 
*** Stack trace of contained exception ***
!ENTRY org.eclipse.ui 4 0 Sep 18, 2002 14:13:11.514
!MESSAGE java.lang.OutOfMemoryError
!STACK 0
java.lang.OutOfMemoryError
	<<no stack trace available>>
!SESSION ----------------------------------------------------------------------
!ENTRY org.eclipse.core.launcher 4 0 Sep 18, 2002 14:15:26.967
!MESSAGE Exception launching the Eclipse Platform:
!STACK
java.lang.OutOfMemoryError
	<<no stack trace available>>
Comment 1 Philipe Mulet CLA 2002-09-20 05:12:07 EDT
What makes you think this is related to JDT/Core ?
Comment 2 Olivier Thomann CLA 2002-09-20 08:49:28 EDT
Use -vmargs -Xmx256M in the command line. This should solve your problem.
Comment 3 Philipe Mulet CLA 2002-10-08 07:00:56 EDT
Closing, as invalid since no evidence JDT/Core is guilty.
Comment 4 Philipe Mulet CLA 2002-10-08 07:01:12 EDT
Closing
Comment 5 Sonia Dimitrov CLA 2002-11-11 10:38:34 EST
*** Bug 25936 has been marked as a duplicate of this bug. ***