From time to time, when building a language, Eclipse crashes with an out of memory error. Eclipse then asks me to exit the workbench. When I restart Eclipse and open a language file, it errors that it cannot identify the language component. Even after building the language, it still cannot identify the language component (my guess: the crash somehow corrupted the build and Spoofax gets confused). What I do then is clean all language projects and building them again.

I’ve now updated Contents/Eclipse/eclipse.ini to use -Xmx2g (instead of -Xmx1g), but maybe the language archiving can be improved to use less memory. Or maybe when restarting Eclipse, we can have it pick up the language (without having to clean and rebuild everything?).

Submitted by Martijn on 20 September 2017 at 20:08