The analyzeFeatureModel in the FeatureDiagramEditor class sets a wrong thread priority, resulting in crashing. In this method, the custom Job mechanism of FeatureIDE is used. I suggest switching it to the Eclipse Job's API (like in the refreshGraphics). The FeatureIDE Job's API uses the Java Thread API and the call of Job.LONG is invalid (Eclipse Platform API).
We fixed this in litcpslab@3d707b0 by removing the call (not necessary).