[MAGNOLIA-7652] OOME when exporting to YAML Created: 14/Oct/19  Updated: 07/Apr/20  Resolved: 16/Oct/19

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 5.5.4, 5.6.5
Fix Version/s: 6.1.3, 6.2

Type: Bug Priority: Neutral
Reporter: Michael Duerig Assignee: Michael Duerig
Resolution: Fixed Votes: 0
Labels: export
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by MAGNOLIA-7655 OOME when exporting to YAML Closed
Problem/Incident
causes MAGNOLIA-7720 JCR Yaml Import is not taking account... Closed
relation
is related to MAGNOLIA-7326 Improve import & export functions to ... Closed
is related to MAGNOLIA-7734 yaml export uses wrong format Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Testcase included:
Yes
Epic Link: Support
Sprint: UI Framework 8
Story Points: 3

 Description   

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



 Comments   
Comment by Michael Duerig [ 14/Oct/19 ]

Preparing a PR

Comment by Michael Duerig [ 16/Oct/19 ]

Merged https://git.magnolia-cms.com/projects/PLATFORM/repos/main/pull-requests/750/overview

Generated at Mon Feb 12 04:25:38 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.