Uploaded image for project: 'Kogito'
  1. Kogito
  2. KOGITO-6076

Stunner - memory leak on selection node

    XMLWordPrintable

Details

    • False
    • False
    • Hide
      1. In VS Code open any process/DMN diagram and open developer tools
      2. enable All Levels logs
      3. Select/Deselect any node several times and check logs

      Actual Result

      1. You will see log about registration on every node selection
      2. You will see growing amount of node deselection event fired on deselection

      Expected Result

      It should be always only one deselection event triggered when a node is deselected.

      Show
      In VS Code open any process/DMN diagram and open developer tools enable All Levels logs Select/Deselect any node several times and check logs Actual Result You will see log about registration on every node selection You will see growing amount of node deselection event fired on deselection Expected Result It should be always only one deselection event triggered when a node is deselected.
    • 2021 Week 40-42 (from Oct 4), 2021 Week 43-45 (from Oct 25)

    Description

      On node select Stunner create event listener for Unselect (ESC button pressed). But it is not destroyed on node deselection.

      As result after some time when you deselect a node it will call dozens of unselect events. See:

      Registration of the event happening there.

      Attachments

        Activity

          People

            jenrique@redhat.com Jaime Enriquez (Inactive)
            kgaevski@redhat.com Kirill Gaevskii
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: