You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Nitin Gupta (Jira)" <ji...@apache.org> on 2020/05/27 06:20:04 UTC

[jira] [Closed] (OAK-8984) A big number of NOOP changes can result in a StackOverflow

     [ https://issues.apache.org/jira/browse/OAK-8984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nitin Gupta closed OAK-8984.
----------------------------

> A big number of NOOP changes can result in a StackOverflow
> ----------------------------------------------------------
>
>                 Key: OAK-8984
>                 URL: https://issues.apache.org/jira/browse/OAK-8984
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: documentmk
>            Reporter: José Andrés Cordero Benítez
>            Assignee: Marcel Reutegger
>            Priority: Minor
>             Fix For: 1.30.0
>
>         Attachments: infinite-recursion-OAK-8984.patch
>
>
> We have a case where a sync job sometimes produce a StackOverflow when a big number of NOOP changes are executed. The problem could be related with the wrapping of a new ModifiedDocumentNodeState object in every call.
> If the number of changes don't reach the UpdateLimit value, if will continue creating objects until it throws a StackOverflow error.
> The problem only happens in very specific conditions, but with help of [~mreutegg] we were able to reproduce in a test that artificially recreates the situation.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)