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

PulseMessagePresenter creating a proper MessageListener introduces a MemoryLeak

    XMLWordPrintable

Details

    • Task
    • Resolution: Fixed
    • Blocker
    • 5.0
    • 5.0
    • None
    • None
    • RC 2

    Description

      Stress-tests revealed we have a potential memory leak. When profiling we found even after logout we have always one AdmincentralUI instance around - together with all it's references. The problem is that in PulseMessagePresenter a proper MessageListener is created that's added to the MessagesManager. As that listener never gets cleaned up the MessageManager stays and with him AdmincentralUI etc...

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              dlipp Daniel Lipp
              dlipp Daniel Lipp
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Checklists

                  Task DoR