Hi Francis,
> The attached patch fixes a memory leak in the JTree, changing a > Hashtable into a WeakHashMap. > > I'm not too familiar with this class, so I don't know if this is the > best way to fix it (or if this even breaks something!), and I'd > appreciate any comments or approval for this patch. This would probably not break things. But using a WeakHashMap doesn't seem like the best solution here. We should rather make sure that no entries are left in the table. I'm thinking that in the TreeModelHandler inner class we can take care of that cleanly without the need to use WeakHashMap. /Roman
