Community
Participate
Working Groups
Build Identifier: 20110615-0604 For the last couple of days I've been regularly (hourly) seeing an IllegalStateException while editing. The exception is followed by garbled dialog boxes (have to force them to redraw by dragging offscreen before their content shows). The affected editor is toast, it shows garbled text and I can't save it. I have to quit Ecipse and then kill the process (it sticks around without any UI). Most recent example, I was editing an unsaved new class file. I think I moved the cursor with the mouse and then started typing. I first saw the problem a day or two ago in eclipse 3.6, I upgraded to 3.7 but I'm using the old workspace. I'll attach the stack trace of the exception. Reproducible: Sometimes
Created attachment 199628 [details] Stack trace
Attached the stack trace. Unfortunately, ProjectionTextStore.get() doesn't populate the exception chain when it throws a new IllegalStateException.
In which editor does it happen? Please attach the entire .log. Do you also see it using http://download.eclipse.org/eclipse/downloads/drops/R-3.7-201106131736/index.php? More precise steps would be appreciated.
I recreated my workspace and the problem seems to have gone away. Haven't seen it for at least a day. I'll attach the log anyway in case it rings any bells.
Created attachment 199758 [details] Full .log file from my broken workspace.
I was using a Java editor. Annoyingly, I couldn't seem to repro the problem at will, it would just happen about once per hour when I was clicked and typed into an editor. I'm doing Android dev so eclipse can be a bit sluggish, maybe the sluggishness was letting me hit a race by typing and clicking too close together. Since (touch-wood) creating a new workspace seems to have cured the problem, maybe you could just add some more diagnostics to the area (chaining the exception would be a good start) so that if it reproduces later we'll get a bit more to go on. The version you suggested for me to try sounds to be older (by a couple of days) than the one I was using but I'd already hit the issue on both 3.6 and (a newer version of) 3.7. Was there a specific reason for trying that exact release?
The log doesn't provide more details that would allow us to find the source of the problem. Marking as WORKSFORME as the problems seems resolved with the new workspace and we can't do much without more detailed steps. > The version you suggested for me to try sounds to be older (by a couple of > days) than the one I was using but I'd already hit the issue on both 3.6 and (a > newer version of) 3.7. Was there a specific reason for trying that exact > release? The indicated download is the pure SDK without additional bundles.
