StackOverflowError in JDTClassNode while editing

This could be another manifestation of the Generics bug associated with enums. Is this the same project you were working on before? Can you send it over again? Or at least tell me where to find the problem (maybe just the single groovy file with the problem is sufficient.

Looking at the stack frames in your error log, and I would say that this is definitely related to enums. However, so far I have not been able to reproduce this myself.

The two bugs that you have uncovered tell me that we are not testing hard enough for enums that are written in Groovy. This is generally a rare situation, but we should have it covered.

Another occurrence, this time with a longer log (stackoverflow2.log) and a better screenshot (stackoverflow-screenshot2.jpeg) of what I was doing when it occurred:
I basically duplicated 3 lines of code by selecting them, Ctrl+C,down arrow, Ctrl-V, and then StackOverflowError!
The three lines of duplicated code have their number still highlighted in the screenshot (lines 136-138, duplicates of the 3 lines above).

Yikes. Lots of interesting stack traces in that error log. It might have to wait until Monday until I can have a deep look into the problem.

Francois - I made a slight adjustment to the resolution of JDTClassNodes. Can you grab a snapshot build and see what difference it makes?

http://dist.codehaus.org/groovy/distributions/greclipse/snapshot/e3.6/

actually I'm not happy with that change, so don't feel you have to try it. I'd prefer to recreate before proceeding.

Ok, I've put in a better set of changes. I have recreated the stackoverflow but only when I force it by getting JDTClassNodes to eagerly initialize themselves. I imagine the editor is causing this initialization to be done when the problem happens in the wild, but it doesn't happen for me. Andrew forwarded me the testcode projects and making simple changes in the file at fault, I can't get it to fail. The fixes address the forced failure scenario I can create, hopefully they will help with the real situation too. Should be in a dev build later today.

Please let us know when you have a chance to try this.

I'm waiting to have a bit more usage before saying it's fine.
I think it is.
When I first had the problem I was spending 30mn on the project here and there and the bug occurred a lot. I'm still juggling with two jobs and I'm not full time on the project where it occurs. I update eclipse everyday and I have to say it's been fine for a few days now.

I also spend some time resolving another problem which probably isn't related: some ClassNotFound on some PowerAssert class or so. In the end I had to remove the groovy 1.8 plugin and run solely on 1.7 to avoid this issue. I think it's because Groovy Monkey includes groovy 1.7 jar.

Bear with me until mid next week and I'll be more confident it's fine.

Thanks for your help.

I see that PowerAssertionError is in different packages for the versions: org.codehaus.groovy.runtime.powerassert for 1.8, but org.codehaus.groovy.transform.powerassert for 1.7. I'm not sure what kinds of affects this would have for you. It could be a problem if your compiler level is 1.8, but you are referencing 1.7 on your classpath (or vice versa).

I had a full day without seeing this error.
Let's close this issue, I'll reopen it if it ever comes back.
Thanks again.

The fix is working, I have not seen this error in a while.