[ 
https://issues.apache.org/jira/browse/OAK-12094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18058413#comment-18058413
 ] 

Julian Sedding edited comment on OAK-12094 at 2/13/26 5:18 PM:
---------------------------------------------------------------

I have applied the change to fix this issue directly to [commit 
251fde2|https://github.com/apache/jackrabbit-oak/commit/251fde23e03a4cc1d92e06a64ff6f52f619295f2]
 in order to verified the fix. It runs to completion with {{-Xmx464m}} and it 
runs OOM with {{-Xmx432m}}, i.e. just like before OAK-12040.

Below are the retained objects of the heap dump caused by this OOM for 
comparison. For me this conclusively shows that the fix removes the regression 
in heap usage.

!retained-objects-after-OAK-12094.png|width=512!


was (Author: jsedding):
I have applied the change to fix this issue directly to [commit 
251fde2|https://github.com/apache/jackrabbit-oak/commit/251fde23e03a4cc1d92e06a64ff6f52f619295f2]
 in order to verified the fix. It runs to completion with {{-Xmx464m}} and it 
runs OOM with {{-Xmx432m}}, i.e. just like before OAK-12040.

Below are the retained objects of the heap dump caused by this OOM for 
comparison. For me this conclusively shows that the fix removes the regression 
in heap usage.

!retained-objects-after-OAK-12094.png|width=560!

> segment-azure: increased heap usage due to OAK-12040
> ----------------------------------------------------
>
>                 Key: OAK-12094
>                 URL: https://issues.apache.org/jira/browse/OAK-12094
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: segment-azure
>            Reporter: Julian Sedding
>            Assignee: Julian Sedding
>            Priority: Minor
>         Attachments: 
> largest-byte-array-incoming-reference-after-OAK-12040.png, 
> retained-objects-after-OAK-12040.png, retained-objects-after-OAK-12094.png, 
> retained-objects-before-OAK-12040.png
>
>
> The change for OAK-12040 accidentally introduced increased heap usage, 
> presumably due to the way the Azure SDK is invoked.
> Running all unit tests in {{oak-segment-azure}} via {{mvn clean test 
> -Dtest.opts.memory=-Xmx496m -pl oak-segment-azure}} reliably causes an 
> {{OutOfMemoryError}} (on my machine using java 21), which wasn't the case 
> before this change.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to