Bug 20531 - ArrayIndexOutOfBoundsException in conjunction with OutOfMemory Problems
Summary: ArrayIndexOutOfBoundsException in conjunction with OutOfMemory Problems
Status: CLOSED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows NT
: P2 critical (vote)
Target Milestone: 3.0 M8   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-06-18 05:19 EDT by Carsten Kaiser CLA
Modified: 2009-08-30 02:21 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Carsten Kaiser CLA 2002-06-18 05:19:04 EDT
The following exception occurs while attempting to rebuild my whole project:

!SESSION Jun 18, 2002 11:16:06.193 ---------------------------------------------
java.version=1.3.1_03
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_GB
Command-line arguments: -os win32 -ws win32 -arch x86 -install file:D:/eclipse/
!ENTRY org.eclipse.core.resources 4 2 Jun 18, 2002 11:16:06.193
!MESSAGE Problems occurred when invoking code from plug-
in: "org.eclipse.core.resources".
!STACK 0
java.lang.ArrayIndexOutOfBoundsException
	at java.lang.System.arraycopy(Native Method)
	at org.eclipse.jdt.internal.compiler.parser.Scanner.getLineEnds
(Scanner.java:1512)
	at 
org.eclipse.jdt.internal.compiler.SourceElementParser.parseCompilationUnit
(SourceElementParser.java:1046)
	at org.eclipse.jdt.internal.core.CompilationUnit.generateInfos
(CompilationUnit.java:363)
	at org.eclipse.jdt.internal.core.CompilationUnit.buildStructure
(CompilationUnit.java:102)
	at org.eclipse.jdt.internal.core.Openable.openWhenClosed
(Openable.java:405)
	at org.eclipse.jdt.internal.core.JavaElement.openHierarchy
(JavaElement.java:523)
	at org.eclipse.jdt.internal.core.JavaElement.getElementInfo
(JavaElement.java:310)
	at org.eclipse.jdt.internal.core.JavaElement.getChildren
(JavaElement.java:264)
	at org.eclipse.jdt.internal.core.JavaElement.getSourceElementAt
(JavaElement.java:427)
	at org.eclipse.jdt.internal.core.CompilationUnit.getElementAt
(CompilationUnit.java:436)
	at 
org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.storeProblemsFor
(AbstractImageBuilder.java:362)
	at 
org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.updateProblemsFor
(AbstractImageBuilder.java:380)
	at 
org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.acceptResult
(AbstractImageBuilder.java:98)
	at org.eclipse.jdt.internal.compiler.Compiler.handleInternalException
(Compiler.java:439)
	at org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:354)
	at org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.compile
(AbstractImageBuilder.java:219)
	at org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.compile
(AbstractImageBuilder.java:166)
	at org.eclipse.jdt.internal.core.builder.BatchImageBuilder.build
(BatchImageBuilder.java:50)
	at org.eclipse.jdt.internal.core.builder.JavaBuilder.buildAll
(JavaBuilder.java:166)
	at org.eclipse.jdt.internal.core.builder.JavaBuilder.build
(JavaBuilder.java:94)
	at org.eclipse.core.internal.events.BuildManager$2.run
(BuildManager.java:386)
	at org.eclipse.core.internal.runtime.InternalPlatform.run
(InternalPlatform.java:802)
	at org.eclipse.core.runtime.Platform.run(Platform.java:416)
	at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:120)
	at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:176)
	at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:186)
	at org.eclipse.core.internal.events.BuildManager$1.run
(BuildManager.java:146)
	at org.eclipse.core.internal.runtime.InternalPlatform.run
(InternalPlatform.java:802)
	at org.eclipse.core.runtime.Platform.run(Platform.java:416)
	at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:160)
	at org.eclipse.core.internal.events.BuildManager.build
(BuildManager.java:232)
	at org.eclipse.core.internal.resources.Project.build(Project.java:88)
	at org.eclipse.ui.actions.BuildAction.invokeOperation
(BuildAction.java:151)
	at org.eclipse.ui.actions.WorkspaceAction.execute
(WorkspaceAction.java:112)
	at org.eclipse.ui.actions.WorkspaceAction$1.execute
(WorkspaceAction.java:269)
	at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run
(WorkspaceModifyOperation.java:64)
	at org.eclipse.core.internal.resources.Workspace.run
(Workspace.java:1361)
	at org.eclipse.ui.actions.WorkspaceModifyOperation.run
(WorkspaceModifyOperation.java:78)
	at org.eclipse.jface.operation.ModalContext$ModalContextThread.run
(ModalContext.java:98)

Currently I'm running stable build F2 since with stable build F3 I encountered 
OutOfMemory exceptions instead while doing the same. So this bug might be 
related to memory problems on my machine respectively caused by the weird 
project I have to work with. Nevertheless it might be worthful examing, whether 
some code within eclipse consumes memory in some kind of loop, which would 
explain this behaviour. My project contains ca. 450 java classes and about 750 
(don"t laugh, it wasn't my idea!) jsp files using weblogic 5.1 sp12.
Comment 1 Jerome Lanneluc CLA 2002-06-18 06:43:28 EDT
This appears to be a problem in the scanner. So it should be reproducible with 
one file. By any chance, do you know which file causes this problem? 
Comment 2 Philipe Mulet CLA 2002-06-20 07:49:20 EDT
Given other bug 20435, you might be experiencing VM issues. Please try to 
reproduce on various platforms and provide exact test case.

Will investigate post 2.0 unless more information is provided.
Comment 3 Philipe Mulet CLA 2004-03-24 12:10:49 EST
Closed as never reproduced in a very long time. Likely a VM artifact.
Comment 4 Denis Roy CLA 2009-08-30 02:21:23 EDT
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.