Not that you'd necessarily be able to do anything about it, but have you tried to run the IDE in debug mode? There's more on it in the Eclipse help section: Force.com IDE Library > Using the Force.com IDE > Reference
Running the Force.com IDE in Debug Mode
If you experience errors in the Force.com IDE, it can be useful to run Eclipse in Debug Mode. This will cause the IDE to write additional information to its system log.
To run the IDE in Debug Mode, add the following parameter to Eclipse's startup command line or in eclipse.ini:
For more information on the Force.com IDE system log, see Force.com Log Viewer.
You can also write the zip file to disk for each save, refresh, synchronize, or deploy action, which can be helpful in diagnosing errors. Add the following parameter to Eclipse's startup command line or in eclipse.ini
Force.com Log Viewer
As the Force.com IDE runs, it writes certain events to a system log file stored in your Eclipse workspace. If you encounter exception messages or other problems while using the IDE, the information in this log file may help you diagnose and resolve the issue. The Force.com Log Viewer provides an easy way to see the contents of the IDE system log or to locate the file so you can provide it to Salesforce customer support.
To show the Force.com Log Viewer:
- In the main menu bar, click Help | Show Force.com IDE Log
You can make the Force.com IDE write more detail to its system log by running the IDE in debug mode. For information, see Running the Force.com IDE In Debug Mode.
In order to show you new events as they occur, the Force.com Log Viewer frequently refreshes itself from the log file on disk. This activity may slow your system, so it is recommended that you keep the Force.com Log Viewer closed during normal use of the IDE.