Bug 112652 - Java Search causes Out of memory exception and crashes workbench
Summary: Java Search causes Out of memory exception and crashes workbench
Status: RESOLVED DUPLICATE of bug 99114
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.2 M6   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-14 12:08 EDT by Janek Lasocki-Biczysko CLA
Modified: 2006-03-14 12:03 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Janek Lasocki-Biczysko CLA 2005-10-14 12:08:55 EDT
on I20051012-1200:

With a Max Heap size of 64 mb (i suggest running a clean runtime workbench, it
defaults to a max heap of 64 mb)

 - import plugin org.eclipse.pde.ui with source
 - preform a java search on "org.eclipse.pde.internal.ui"
   - search for: TYPE
   - limit to: ALL occurences

the operation should crash the workbench with the following appearing in .log
!SESSION 2005-10-14 12:01:05.003 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.4.2_06
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments:  -product org.eclipse.sdk.ide -pdelaunch
Command-line arguments:  -product org.eclipse.sdk.ide -data E:\runtime-workbench
-dev
file:e:/workspace/.metadata/.plugins/org.eclipse.pde.core/New_configuration/dev.properties
-pdelaunch -os win32 -ws win32 -arch x86

!ENTRY org.eclipse.core.runtime 4 2 2005-10-14 12:05:24.937
!MESSAGE An internal error occurred during: "Java Search".
!STACK 0
java.lang.OutOfMemoryError

!ENTRY org.eclipse.ui 4 4 2005-10-14 12:05:25.391
!MESSAGE Unhandled event loop exception

!ENTRY org.eclipse.ui 4 0 2005-10-14 12:05:25.391
!MESSAGE java.lang.OutOfMemoryError
!STACK 0
java.lang.OutOfMemoryError
Comment 1 Frederic Fusier CLA 2005-10-14 12:24:53 EDT

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