#19 Setting a new default tree synthesizer produces zombies

[Christoph Müller]

When a new default tree synthesizer is set in the
TreeManager using setDefaultTreeSynthesizer, the old
default tree synthesizer is not removed as listener from
the TreeManager. This has the result that the old
synthesizer is invoked on every ModelChangedEvent but
the results are discarded. Setting new default tree
synthesizers therefore results in a significant loss of
performance.

There is the following workaround for the problem:

treeManager.removeModelChangedListener
(treeManager.getDefaultTreeSynthesizer());
treeManager.setDefaultTreeSynthesizer
(newSynthesizer);

[Anonymous]

Logged In: YES
user_id=1004466

fixed in AbstractTreeSynthesizer's setTreeManager(...) method