[GROOVY-1654] Groovy Eclipse Editor pegs CPU to 100% when editing certain .groovy files on linux

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.0
• Fix Version/s: 1.0
• Environment: Ubuntu Edgy Linux; Eclipse 3.2.1
• Assignee: Guillaume Sauthier
• Reporter: Cameron Braid
• Created: 15/Jan/07 20:46
• Updated: 21/Dec/09 06:49
• Resolved: 16/Jan/07 16:43

Description

Editing certain .groovy classes using the eclipse plugin causes uses 100% cpu

org/test/A.groovy is a class A in package org.test that extends org.test.B
org/test/B.groovy is a class B in package org.test that extends org.test.C
org/test/C.groovy is a class C that imports and uses a class that isn't on the classpath (unknown.Thing)

Editing A or B cases 100% CPU usage

The interesting thing is that if I start eclipse, then create this system, there is no issue. Then, if I restart eclipse, then edit A or B the issue arises.