You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "mingleizhang (JIRA)" <ji...@apache.org> on 2017/11/06 06:17:00 UTC
[jira] [Commented] (COLLECTIONS-599) HashEntry array object naming
data initialized with double the size during deserialization
[ https://issues.apache.org/jira/browse/COLLECTIONS-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16239959#comment-16239959 ]
mingleizhang commented on COLLECTIONS-599:
------------------------------------------
Does anyone give me a permission that can contribute code to apache/commons ? Thank you very much! Minglei.
> HashEntry array object naming data initialized with double the size during deserialization
> ------------------------------------------------------------------------------------------
>
> Key: COLLECTIONS-599
> URL: https://issues.apache.org/jira/browse/COLLECTIONS-599
> Project: Commons Collections
> Issue Type: Bug
> Components: Collection, Map
> Affects Versions: 3.1
> Reporter: Tejas Patel
> Priority: Critical
> Fix For: 4.1
>
>
> Common collections 3.1 and 3.2 are used at many places and frameworks including struts2.
> Supose a LinkedMap object it is created and have size greater than zero is serialized. While deserializing this object , array of HashEntry naming data delacred in AbstractHashedMap always initialises with a new capacity of double its double of the serialized object.
> Please see the below API declared in AbstractHashedMap class :
> protected void checkCapacity()
> {
> if (this.size >= this.threshold)
> {
> int newCapacity = this.data.length * 2;
> if (newCapacity <= 1073741824) {
> ensureCapacity(newCapacity);
> }
> }
> }
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)