[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: |
|
||||||||||||||||
| 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 |