Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 347747 - To much null objects in HashMap
Summary: To much null objects in HashMap
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: BIRT (show other bugs)
Version: unspecified   Edit
Hardware: PC All
: P3 critical (vote)
Target Milestone: 3.7.1   Edit
Assignee: Xuelan Li CLA
QA Contact: Xiaoying Gu CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-31 05:18 EDT by Jan Lerby CLA
Modified: 2011-06-10 04:15 EDT (History)
1 user (show)

See Also:

Attachments
Excerpt a typical HashMap (62.37 KB, image/jpeg)
2011-05-31 05:19 EDT, Jan Lerby CLA 		no flags Details
View All 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 Jan Lerby CLA 2011-05-31 05:18:36 EDT 
Build Identifier: 20110218-0911

Hi,

we had memory problems with BIRT 2.6.2 and look for reason. During searching we have noticed that BIRT makes MANY HashMaps of report objects. The point of this bug is HashMaps have default size 16 items. Even if all items are null. And it contributes to consuming memory to crash.
I think better is to set size HashMap for 3 items. In most cases HashMap has 0 or 1 item. Less common is 2 or 3 items. And more than 3 items it is rarely.
I am adding picture of typical HashMap object.
HashMap is created in org.eclipse.birt.report.model.core.DesignElement for field propValues
protected Map<String, Object> propValues = new HashMap<String, Object>( );



Reproducible: Always
Comment 1 Jan Lerby CLA 2011-05-31 05:19:32 EDT 
Created attachment 196969 [details]
Excerpt a typical HashMap
Comment 2 Xuelan Li CLA 2011-06-10 04:15:04 EDT 
fixed.