[
https://issues.apache.org/jira/browse/OAK-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manfred Baedke updated OAK-4568:
--------------------------------
Labels: candidate_oak_1_0 candidate_oak_1_2 observation (was:
candidate_oak_1_0 candidate_oak_1_2 candidate_oak_1_4 observation)
> JournalEntry.applyTo() creates complete change tree in memory
> -------------------------------------------------------------
>
> Key: OAK-4568
> URL: https://issues.apache.org/jira/browse/OAK-4568
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, documentmk
> Affects Versions: 1.0, 1.2, 1.4
> Reporter: Marcel Reutegger
> Assignee: Marcel Reutegger
> Labels: candidate_oak_1_0, candidate_oak_1_2, observation
> Fix For: 1.6, 1.5.6, 1.4.8
>
>
> While applying the changes from {{StringSort}} to the diff cache, the method
> recreates the entire change tree in memory. Depending on the revision range,
> the number of changes can be very high and cause an OOME.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
