Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-7655

OOME when exporting to YAML

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Neutral
    • Resolution: Fixed
    • Affects Version/s: 5.5.4, 5.6.5
    • Fix Version/s: 5.5.16, 5.6.12, 5.7.6, 6.1.3
    • Component/s: core
    • Labels:
    • Testcase included:
      Yes
    • Release notes required:
      Yes
    • Epic Link:
    • Sprint:
      UI Framework 8, Release 6.1.3 & Content API RM
    • Story Points:
      3
    • Magnolia Release:
      5.5.16, 5.6.13, 5.7.6, 6.1.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

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              mduerig Michael Duerig
              Reporter:
              mduerig Michael Duerig
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Date of First Response: