Eclipse Community Forums: TMF (Xtext) » Is there a memory leak of xtext editors opened by debugger?

Help

Home

Home » Modeling » TMF (Xtext) » Is there a memory leak of xtext editors opened by debugger?

Show: Today's Messages :: Show Polls :: Message Navigator

Is there a memory leak of xtext editors opened by debugger? [message #1219274]

Tue, 03 December 2013 05:43

paul lu

Messages: 43
Registered: April 2013

Member

Hi,

The debug framework uses SourceLookupFacility to open the source code editor. It can set the editor input using one instantiated editor part. But there is no way to call xtext editor's dispose, does it mean no way to undo "set editor input" and release the memory ? BTW, why the dispose does many null assignments?

I experimented with xtend, the source editor first turned out to be java editor; I opened xtend editors and set a few breakpoints, then the debug displays the xtend editors (why?). After repeating the debugging to make the editor input switch as much as possible, the memory did increase. Is it a problem ?

Thanks !

Report message to a moderator

Previous Topic:	EMF + Xtext 2.4.3: Error in serialization of EObject
Next Topic:	Optimize imports on content proposal

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 11:43:00 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter