| [xcore] Disabling auto-build of xcore [message #1419288] |
Mon, 08 September 2014 11:27  |
 Phillip Keldenich
Messages: 9
Registered: January 2014 |
Junior Member |
|
|
There already is an existing (but very old) forum thread regarding this, but the issue arised for me as well:
Is there (by now) any way to disable the automatic build (i.e. the automatic regeneration of code) on an XCore model change?
I do not want to turn off automatic building completely (because that would affect Java code as well), but the XCore builder takes huge amounts of time on a model file with ~1000 lines; this freezes the XCore editor (and often eclipse as well), sometimes literally for several minutes, after every change, often while typing (even in comment-only changes).
I do not know whether the build should be done in parallel with the editing, but maybe it is the garbage collector that leads to the freeze - sometimes after editing the XCore model for a "longer" time (30 minutes or so), I get a GC overhead limit exceeded exception and Eclipse advises me to close the entire thing.
Moreover, this drastically decreases the running time of Laptop batteries when you use XCore without power supply (train ride, ...)
This really makes using the XCore editor a pain - I actually switched to an external editor without proper syntax highlighting for XCore. Btw, are there any syntax highlighting plugins for XCore for Vim or Notepad++ (or other text editors like GEdit, ...)?
Overall (if this is not already implemented), I would recommend to implement this feature.
Edit: The freeze indeed seems to stem from the fact that eclipse ran into memory pressure (when using 1GB max heap size - is this expected for a 1k lines file, when the heap size after a fresh start is about 260 MB?)
When using 2GB max heap size the problem is not as big anymore and the editor is usable again.
[Updated on: Mon, 08 September 2014 11:51] Report message to a moderator |
|
|
| Re: [xcore] Disabling auto-build of xcore [message #1419314 is a reply to message #1419288] |
Mon, 08 September 2014 12:16  |
Ed Merks
Messages: 33133
Registered: July 2009 |
Senior Member |
|
|
Phillip,
Comments below.
On 08/09/2014 1:27 PM, Phillip Keldenich wrote:
> There already is an existing (but very old) forum thread regarding
> this, but the issue arised for me as well:
> Is there (by now) any way to disable the automatic build (i.e. the
> automatic regeneration of code) on an XCore model change?
>
> I do not want to turn off automatic building completely (because that
> would affect Java code as well), but the XCore builder takes huge
> amounts of time on a model file with ~1000 lines; this freezes the
> XCore editor (and often eclipse as well), sometimes literally for
> several minutes, after every change, often while typing (even in
> comment-only changes).
But that's not the build, that's model inference. Without that, you
might as well use a text editor.
>
> I do not know whether the build should be done in parallel with the
> editing, but maybe it is the garbage collector that leads to the
> freeze - sometimes after editing the XCore model for a "longer" time
> (30 minutes or so), I get a GC overhead exceeded exception and Eclipse
> advises me to close the entire thing.
Builds should only kick in when you save...
>
> Moreover, this drastically decreases the running time of Laptop
> batteries when you use XCore without power supply (train ride, ...)
>
> This really makes using the XCore editor a pain - I actually switched
> to an external editor without proper syntax highlighting for XCore.
> Btw, are there any syntax highlighting plugins for XCore for Vim or
> Notepad++ (or other text editors like GEdit, ...)?
Perhaps you can try updating to
http://download.eclipse.org/modeling/emf/emf/updates/2.10.x/
This contains a large number of performance fixes to the inference
infrastructure as well as fixes to properties view updates and outline
updates which hopefully completely eliminate the problems you're
seeing. Please give it a try. There remains a bug in auto completion
of imports in this version that I'm working on now, so hopefully that's
not too annoying; it will be fixed in Wednesday's build. There might
still be a memory leak as well, but closing and reopening the editor
periodically should work around that... Hopefully I'll have some time to
look into this as well.
In any case, please try updating and please let me know if you continue
to see significant performance problems.
>
> Overall (if this is not already implemented), I would recommend to
> implement this feature.
>
>
>
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Powered by
FUDForum. Page generated in 0.02527 seconds
] 
Search
Help
Register
Login
Home
