[
https://issues.apache.org/jira/browse/OAK-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15350466#comment-15350466
]
Marcel Reutegger commented on OAK-4503:
---------------------------------------
In some cases, like the one with frequent lock() calls, the memory usage will
indeed go up. Without rebase() calls, either explicitly or by some other JCR
calls, the memory usage will still be the same. I'll add a sentence in the
release notes about this when I commit the fix.
> Update count increases with rebase
> ----------------------------------
>
> Key: OAK-4503
> URL: https://issues.apache.org/jira/browse/OAK-4503
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, documentmk
> Affects Versions: 1.0, 1.2, 1.4
> Reporter: Marcel Reutegger
> Assignee: Marcel Reutegger
> Priority: Minor
> Fix For: 1.6
>
>
> The update count in {{DocumentRootBuilder}} increases with the number of
> changes in memory when {{rebase()}} is called. The update count should stay
> the same because a rebase does not affect the number of in-memory changes.
> This may lead to premature creation of a branch when pending changes are
> rebased too often. E.g. when Node.isLocked() is called frequently.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
