[MAGNOLIA-7655] OOME when exporting to YAML Created: 16/Oct/19  Updated: 20/Dec/19  Resolved: 21/Oct/19

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

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
clones MAGNOLIA-7652 OOME when exporting to YAML Closed
relation
is related to MAGNOLIA-7326 Improve import & export functions to ... 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
Release notes required:
Yes
Date of First Response:
Epic Link: Support
Sprint: UI Framework 8, Release 6.1.3 & Content API RM
Story Points: 3

 Description   

Backport of the fix delivered in the cloned ticket.


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 Federico Grilli [ 29/Oct/19 ]

mdrapela/docuteam
As we did for 6.1.3, I guess it's worth mentioning the API break in a minor release for the greater good.

https://documentation.magnolia-cms.com/display/DOCS61/Release+notes+for+Magnolia+CMS+6.1.3#ReleasenotesforMagnoliaCMS6.1.3-Outofmemorywhenexportinglargedata

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