Description of problem: A completely bizzare bug. Opening up eclipse it hung for a few minutes, taking the whole machine with it so that mouse movement was very choppy. After a few minutes it subsided and I started actually seeing a progress bar. After that eclipse opened up and I had a message from the latest eclipse-bugzilla, the message was the same that we were getting with GCC4.1 (when it tries to refresh the repository metadata). Then one of the Java files that was previously opened could not be opened with the following error message displayed *inside* that editor's tab: " Unable to create this part due to an internal error. Reason for the failure: The editor class could not be instantiate. This usually indicates that the editor's class name was mistyped in plugin.xml. " When clicking on the "Details" plugin I get a huge stack trace, which I am attaching. I'll try to reproduce this but it looks like a very weird anomaly. Version-Release number of selected component (if applicable): gcc-4.0.2-8.fc4.i386 eclipse-platform-3.1.1-1jpp_1fc.FC4.12.i386 java-1.4.2-gcj-compat-1.4.2.0-40jpp_31rh.FC4.2.i386 How reproducible: Not directly reproducible so far, but bugging just in case it comes up again. Steps to Reproduce: Actual results: Expected results: Additional info:
Created attachment 123505 [details] stack trace
Should we leave this open? You mentioned it's difficult to reproduce ...
We can close it, I just filed it in case it ever comes up which it seems it won't.
(In reply to comment #3) > We can close it, I just filed it in case it ever comes up which it seems it won't. Okay, thanks.