MUI: Possible Memory Leak causing significant Performance Regression

Feedback & Ideas Implemented Fixes
1

Hi,

in regard to the ongoing performance conversation amongst the Star Alliance I want top bring to your attention a possible memory leak.

Reproduction

  1. Start Knime via Shell .\knime.exe --remote-debugging-port=9222
  2. Inspect it in Chrome and observe the Performance Monitor
  3. Create an empty workflow > Place a table creator > Wrap it into a Meta Node
  4. Open the Meta Node and replicate the Table creator 100 times
  5. Open then Close and repeat 10 times > Close Workflow > Repeat the opening-close procedure

There clearly seems to be something wrong as the amount of DOM-Node count, Event Listeners, and consequentially memory usage is only going up.

Considering that the JavaScript-based UI only leverages one CPU core and rendering is also done on it, performance is expectably diminishing over the course of using Knime.

Neither save & closing the workflow nor running Garbage Collectors seems to work

Screenshot 2025-02-04 075049 Open Close Meta Node 10 times in two sequences with closing Workflow in between
Screenshot 2025-02-04 075049 Open Close Meta Node 10 times in two sequences with closing Workflow in between2557×1392 185 KB

Archive with screenshots, heap- and thread dump (download valid until Feb. 11th)

Best
Mike

1 Like
2

Thank you @mwiegand for reporting this problem!
I created a ticket (NXT-3327) and this topic will get updated as soon as the ticket is done and closed.

4 Likes
5

Internal ticket ID: NXT-3327
Summary: Memory leak in MUI when rendering workflows
Fix version(s): 5.4.1, 5.5.0

2 Likes