On Mon, 28 Apr 2025 09:20:38 GMT, Aleksey Shipilev wrote:
>> CDS cannot handle large number of classes, because `ClassLoader` data
>> structures get too large for CDS archival. The new test captures such an
>> occasion. We do `clear()`-s, but that is not enough to trim the backing
>> storages
On Mon, 28 Apr 2025 09:20:38 GMT, Aleksey Shipilev wrote:
>> CDS cannot handle large number of classes, because `ClassLoader` data
>> structures get too large for CDS archival. The new test captures such an
>> occasion. We do `clear()`-s, but that is not enough to trim the backing
>> storages
On Mon, 28 Apr 2025 09:20:38 GMT, Aleksey Shipilev wrote:
>> CDS cannot handle large number of classes, because `ClassLoader` data
>> structures get too large for CDS archival. The new test captures such an
>> occasion. We do `clear()`-s, but that is not enough to trim the backing
>> storages
On Mon, 28 Apr 2025 09:20:38 GMT, Aleksey Shipilev wrote:
>> CDS cannot handle large number of classes, because `ClassLoader` data
>> structures get too large for CDS archival. The new test captures such an
>> occasion. We do `clear()`-s, but that is not enough to trim the backing
>> storages
On Fri, 25 Apr 2025 20:54:21 GMT, John R Rose wrote:
>> Aleksey Shipilev has updated the pull request with a new target base due to
>> a merge or a rebase. The incremental webrev excludes the unrelated changes
>> brought in by the merge/rebase. The pull request contains four additional
>> comm
On Sun, 27 Apr 2025 20:32:24 GMT, Andrey Turbanov wrote:
>> Aleksey Shipilev has updated the pull request with a new target base due to
>> a merge or a rebase. The incremental webrev excludes the unrelated changes
>> brought in by the merge/rebase. The pull request contains four additional
>>
> CDS cannot handle large number of classes, because `ClassLoader` data
> structures get too large for CDS archival. The new test captures such an
> occasion. We do `clear()`-s, but that is not enough to trim the backing
> storages for the affected collections.
>
> In contrast with previous att
On Fri, 25 Apr 2025 14:49:37 GMT, Aleksey Shipilev wrote:
> CDS cannot handle large number of classes, because `ClassLoader` data
> structures get too large for CDS archival. The new test captures such an
> occasion. We do `clear()`-s, but that is not enough to trim the backing
> storages for
On Fri, 25 Apr 2025 14:49:37 GMT, Aleksey Shipilev wrote:
> CDS cannot handle large number of classes, because `ClassLoader` data
> structures get too large for CDS archival. The new test captures such an
> occasion. We do `clear()`-s, but that is not enough to trim the backing
> storages for
On Fri, 25 Apr 2025 14:49:37 GMT, Aleksey Shipilev wrote:
> CDS cannot handle large number of classes, because `ClassLoader` data
> structures get too large for CDS archival. The new test captures such an
> occasion. We do `clear()`-s, but that is not enough to trim the backing
> storages for
On Fri, 25 Apr 2025 14:49:37 GMT, Aleksey Shipilev wrote:
> CDS cannot handle large number of classes, because `ClassLoader` data
> structures get too large for CDS archival. The new test captures such an
> occasion. We do `clear()`-s, but that is not enough to trim the backing
> storages for
On Fri, 25 Apr 2025 14:49:37 GMT, Aleksey Shipilev wrote:
> CDS cannot handle large number of classes, because `ClassLoader` data
> structures get too large for CDS archival. The new test captures such an
> occasion. We do `clear()`-s, but that is not enough to trim the backing
> storages for
> When lots of classes are loaded during `java -Xshare:dump`, the internal
> arrays used by some of the HashMaps and ArrayLists become too large to be
> archived by CDS (> 256KB).
>
> At the very end of Java bytecode execution during `java -Xshare:dump`, we
> used to call `clear()` on these tab
On Thu, 31 Oct 2024 09:16:00 GMT, Aleksey Shipilev wrote:
>> When lots of classes are loaded during `java -Xshare:dump`, the internal
>> arrays used by some of the HashMaps and ArrayLists become too large to be
>> archived by CDS (> 256KB).
>>
>> At the very end of Java bytecode execution duri
On Thu, 31 Oct 2024 03:52:16 GMT, Ioi Lam wrote:
> When lots of classes are loaded during `java -Xshare:dump`, the internal
> arrays used by some of the HashMaps and ArrayLists become too large to be
> archived by CDS (> 256KB).
>
> At the very end of Java bytecode execution during `java -Xsha
On Thu, 31 Oct 2024 03:52:16 GMT, Ioi Lam wrote:
> When lots of classes are loaded during `java -Xshare:dump`, the internal
> arrays used by some of the HashMaps and ArrayLists become too large to be
> archived by CDS (> 256KB).
>
> At the very end of Java bytecode execution during `java -Xsha
When lots of classes are loaded during `java -Xshare:dump`, the internal arrays
used by some of the HashMaps and ArrayLists become too large to be archived by
CDS (> 256KB).
At the very end of Java bytecode execution during `java -Xshare:dump`, we used
to call `clear()` on these tables to free
17 matches
Mail list logo
