Bug 21723

Summary:

Getting java.lang.OutOfMemoryError

Product:

[Eclipse Project] JDT

Reporter:

Deepu Bhatia <deepu_bhatia2000>

Component:

Core

Assignee:

Philipe Mulet <philippe_mulet>

Status:

RESOLVED WONTFIX

QA Contact:

Severity:

critical

Priority:

CC:

deepu_bhatia2000

Version:

2.0

Target Milestone:

2.1 M1

Hardware:

OS:

Windows 2000

Whiteboard:

Attachments:

Description	Flags
This is the error log file showing the OutOfMemory exception	none

Description Deepu Bhatia

2002-07-18 22:03:35 EDT

I am attempting to create a new project on an existing codebase. I am using 
the "New Java project" option through the wizard. While trying to examine the 
codebase, I am getting a message box stating "An internal error occurred". The 
title of the message box states "Build Problems".
I am getting this error consistently with the 2.0 release.

I am putting a copy of the error log here:

!SESSION Jul 18, 2002 19:04:28.204 ---------------------------------------------
java.version=1.3.1_03
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/
!ENTRY org.eclipse.ui 4 4 Jul 18, 2002 19:04:28.204
!MESSAGE Exception in org.eclipse.ui.actions.BuildAction. run: 
java.lang.OutOfMemoryError
!ENTRY org.eclipse.ui 4 4 Jul 18, 2002 19:04:28.214
!MESSAGE Exception in org.eclipse.ui.actions.BuildAction. run: 
java.lang.OutOfMemoryError
!STACK 0
java.lang.OutOfMemoryError
	<<no stack trace available>>
!ENTRY org.eclipse.jdt.ui 4 1 Jul 18, 2002 19:05:14.190
!MESSAGE Internal Error
!STACK 0
java.lang.reflect.InvocationTargetException: java.lang.OutOfMemoryError
	<<no stack trace available>>

Comment 1 Deepu Bhatia

2002-07-18 22:05:35 EDT

Created attachment 1715 [details]
This is the error log file showing the OutOfMemory exception

Comment 2 Deepu Bhatia

2002-07-19 20:54:59 EDT

I changed the JDK version from 1.3.1_04 to 1.4_01. I am able to compile the 
project perfectly well now. At the bare minimum we should at least update 
release notes to document that using JDK 1.3 might give problems.

Comment 3 Philipe Mulet

2002-07-22 08:10:36 EDT

What are your memory settings ? You are simply seeing a VM issue which occurs 
if you don't give it enough memory. Use the "-Xmx250Mb" command line arguments 
(behind -vmargs).

Comment 4 Deepu Bhatia

2002-07-22 14:30:32 EDT

Yes, you r right. This is a VM memory issue and not an Eclipse bug. I provided 
the "-Xmx250Mb" command line arg and that solved the problem on JDK 1.3.1.
Many thanks.

Comment 5 Philipe Mulet

2002-07-25 07:39:07 EDT

Closing, not fixed.

Comment 6 Philipe Mulet

2002-07-25 07:39:21 EDT

Closed