Community
Participate
Working Groups
build N0222 I was editing some text in a java editor and believe that I attempted to save and then switch to another editor when Eclipse locked up consuming 100% of the CPU. Attached it the full stack dump using ctrl-break.
Created attachment 8106 [details] full stack trace from lockup
The stack trace shows that the main thread waits for a condition when creating a char array and using a private non-synchronized field. To me it looks as if the dump is corrupt or it's a VM problem. We can't do much here.
Keeping as REMIND to be reopened when we have more info.
Get rid of deprecated state.
.