-
Bug
-
Resolution: Fixed
-
Neutral
-
5.5.4, 5.6.5
-
-
Empty show more show less
-
Yes
-
UI Framework 8
-
3
Exporting sufficiently large workspaces to YAML cause an OOME. To reproduce run
mvn clean verify -Dtest=JcrExportLargeWorkspaceTest -Djcrexport.verbose=true -DfailIfNoTests=false -Djcrexport.format=yaml -Djcrexport.nodes.count=1000000
From PR #746 and watch the JVM spending most time in full gc cycles eventually going OOM
Acceptance criteria
- causes
-
MAGNOLIA-7720 JCR Yaml Import is not taking account of null properties
- Closed
- is cloned by
-
MAGNOLIA-7655 OOME when exporting to YAML
- Closed
- is related to
-
MAGNOLIA-7326 Improve import & export functions to avoid OOM error
- Closed
-
MAGNOLIA-7734 yaml export uses wrong format
- Closed