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
Issue Log
r24303
should provide at least a partial fix, addressing the issue forStrategoObserver
s/DebuggableHybridInterpreter
s 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.
Apparently
StrategoObserverBackgroundUpdateJob
can’t callStrategoObserver.uninit()
, so as a new work-around I now disabled the debugger usingEnvironment.DEBUG_INTERPRETER_ENABLED = false
.
Marking this issue as closed;
1.02
and1.09
work 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