on x-document and x-noderef
via session:handle?????
thx
Hi Rudy,
The best way to find memory leaks is using the debugger. The debugger has a feature called 'dynamic object tracking'. The dynamic object tracking shows which objects have been created in memory from the time object tracking is turned on and where they were created.
kind of hard to do without knowing anything about the program.
but widget-pools can also be pretty useful, again, depending.