Bug 67786 - OutOfMemoryError searching for reference to Object
Summary: OutOfMemoryError searching for reference to Object
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.0 RC3   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords: performance
Depends on:
Blocks:
 
Reported: 2004-06-18 06:00 EDT by Jerome Lanneluc CLA
Modified: 2004-06-18 07:43 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jerome Lanneluc CLA 2004-06-18 06:00:08 EDT 
I20040617

1. Start new workspace on JDK 1.4.2 with VM defaults (i.e. not increasing the 
default heap size)
2. Import all sdk plugins as binary linked projects
3. Open java.lang.Object
4. Search for references to Object in workspace
Observe: Near the end of the search, you get an OutOfMemoryError.
Comment 1 Philipe Mulet CLA 2004-06-18 07:10:53 EDT 
One trivial change could be made so as to accomodate VM defaults: simply 
reduce the amount of units processed at once by our match locator.
Currently, we batch 500 units at once.

Pls investigate, if trivial fix works, then +1 for RC3.
Comment 2 Jerome Lanneluc CLA 2004-06-18 07:13:16 EDT 
Decreasing the amount of units processed at once to 425 makes the 
OutOfMemoryError go away. 400 seems like a reasonable number.
Comment 3 Dirk Baeumer CLA 2004-06-18 07:17:00 EDT 
+1 Dirk.
Comment 4 Philipe Mulet CLA 2004-06-18 07:31:30 EDT 
Change reviewed.
Comment 5 Jerome Lanneluc CLA 2004-06-18 07:43:04 EDT 
Changed MatchLocator.MAX_AT_ONCE to 400.