Uploaded image for project: 'Magnolia UI'
  1. Magnolia UI
  2. MGNLUI-4004

Asynchronous actions can consume a lot of memory

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Critical
    • 5.3.17, 5.4.10, 5.5
    • 5.3.9, 5.4.x
    • None
    • None
    • Yes
    • Basel 61
    • 5

    Description

      The inner class AbstractCommandAction.CommandActionTriggerListener is not declared static and hence each instance is bound to the parent action object. This action object has references to UI related objects. This way the asynchronous tasks in the scheduler use much more heap than needed which makes the GCs job unnecessary hard.

      We have seen a system where this added up to 1Gigabite of heap.

      If I am right then adding the static modifier to the inner class would be enough.

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              fgrilli Federico Grilli
              pbaerfuss Philipp Bärfuss
              Votes:
              2 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Checklists

                  Bug DoR
                  Task DoD

                  Time Tracking

                    Estimated:
                    Original Estimate - Not Specified
                    Not Specified
                    Remaining:
                    Remaining Estimate - 0d
                    0d
                    Logged:
                    Time Spent - 2d 3.5h
                    2d 3.5h