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

On 13 February 2012 at 17:44 Gabriël Konat tagged @lennartkats

On 13 February 2012 at 17:49 Lennart Kats tagged @rickylindeman

On 13 February 2012 at 17:52 Lennart Kats commented:

r24303 should provide at least a partial fix, addressing the issue for StrategoObservers/DebuggableHybridInterpreters loaded by editors and background jobs.


On 13 February 2012 at 17:59 Gabriël Konat commented:

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.


On 13 February 2012 at 18:01 Lennart Kats tagged 1.1

On 13 February 2012 at 18:01 Lennart Kats tagged interesting

On 13 February 2012 at 18:20 Lennart Kats tagged runtime

On 13 February 2012 at 18:59 Lennart Kats commented:

Apparently StrategoObserverBackgroundUpdateJob can’t call StrategoObserver.uninit(), so as a new work-around I now disabled the debugger using Environment.DEBUG_INTERPRETER_ENABLED = false.


On 15 February 2012 at 15:58 Lennart Kats tagged error

On 15 February 2012 at 15:58 Lennart Kats tagged error

On 15 February 2012 at 15:58 Lennart Kats tagged 1.0.2

On 15 February 2012 at 15:58 Lennart Kats removed tag 1.1

On 16 February 2012 at 17:56 Lennart Kats closed this issue.

On 16 February 2012 at 17:56 Lennart Kats commented:

Marking this issue as closed; 1.02 and 1.09 work around this. The next version that re-enables the debugger will use a new model based on weak references for lightweight listeners.


On 16 February 2012 at 17:56 Lennart Kats tagged @gohla

On 16 February 2012 at 22:11 Ricky Lindeman commented:

I removed the ILaunchListener completely, it was not used by the debugger.


On 22 February 2012 at 16:36 Lennart Kats removed tag interesting

Log in to post comments