Memory leak from DebuggableHybridInterpreter
DebuggableHybridInterpreter objects are still referenced by an Eclipse listener even if they are not used any more, causing a memory leak.Submitted by Gabriël Konat on 13 February 2012 at 17:44
r24303should provide at least a partial fix, addressing the issue for
DebuggableHybridInterpreters loaded by editors and background jobs.
r24303 seems to have fixed it for the most part, memory usage dropped down to normal levels after a garbage collection. But there could still be cases where they won’t be collected.
StrategoObserver.uninit(), so as a new work-around I now disabled the debugger using
Environment.DEBUG_INTERPRETER_ENABLED = false.
Marking this issue as closed;
1.09work around this. The next version that re-enables the debugger will use a new model based on weak references for lightweight listeners.
I removed the ILaunchListener completely, it was not used by the debugger.
Log in to post comments