]
Andre Dietisheim commented on JBIDE-22315:
------------------------------------------
This should only be true for the wizard where it is used via the new server wizard
framework of wst (when launching from New->Server in the Servers view or from
File->New->...). The root cause is that the wst framework for wizard fragments loads
extensions and caches them. That's actually also the core reason for them using a task
model.
Application wizard: memory leak
-------------------------------
Key: JBIDE-22315
URL:
https://issues.jboss.org/browse/JBIDE-22315
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.4.0.Alpha1
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Priority: Critical
Labels: application_wizard, openshift_v3
Fix For: 4.4.0.Alpha2
Each instance of the wizard with pages, models, data binding contexts, and all referenced
objects, including openshift model objects remains in memory. Disposed are only SWT
widgets, but even they are not ready for the garbage collector since they remain
referenced by data binding contexts.