If I accidentally have a strategy that loops indefinitely, Eclipse freezes up and the only thing I can do is kill it and restart. Although I understand why this happens, I do not like and this should be fixed :)

Submitted by Zef Hemel on 16 March 2010 at 13:13

This is related to issue Spoofax/8: Run builders and on save handler in a separate thread/job.

I haven’t really seen this problem recently though, since I added a loop detector to the repeat(s) strategy (after Maartje first found this issue). Other strategies that cause loops eventually throw a StackOverflowError. So maybe you wrote a special kind of loop? :)

Maybe I should just be more patient and wait for the StackOverflowError… :)

This gets more annoying when content completion (which runs in the UI thread) has to wait for the loop to finish: Spoofax/60.

UI-wise I suppose the console would have to get a “stop” button for this.

I’m still not sure what to do about content completion though: if the content completion thread (i.e., the main UI thread) has to wait for our background thread to finish, Eclipse would still lock up…

Implemented in r21089. What remains is some way to avoid loops in reference resolving and content completion (Spoofax/197).