Eclipse’s fundamental windowing toolkit is SWT - any custom Swing code is, at the end of the day, being shoe-horned into SWT.
So everything you do in KNIME UI-wise is SWT-based.
Ideally (not generally, but for this situation) you have workflows that you have been working with in which you’ve been experiencing freezing. In this situation:
- startup KNIME
- open one of those workflows
- execute it once
- take a snapshot in Sleak
- execute it again
- do a diff in Sleak
- see if there are notable numbers of Image or GC instances listed
- if there are, take another snapshot to set the baseline and repeat this for subsections of the workflow in order to try to determine if there are specific nodes, or configurations of nodes (like loops) which are the source of these continued instance generation