Geek Answers Handbook

Eclipse 3.6 autocomplete eclipse / quick fix

I have a problem that seems to occur with both autocomplete and quick fix. Sometimes, when I use cmd + 1 for a quick fix, Eclipse freezes and no matter how long I wait (at least 30 minutes), nothing happens. When checking activity on the monitor, it shows almost no processor activity.

I have a Mac with OSX 10.6 and Helios without any weird plugins. I program in java, so I use very standard functions.

Is this a known bug? I searched a lot on Google to find useful information. I am not very good at reporting bug reports, and the concept of the freeze function changes my search results.

Thanks for any help.

+6
java eclipse freeze
source share
2 answers

As for Eclipse, you may not know what is going on. The entire platform is a set of plugins, and the requirements (e.g. responsiveness) are not strict for them. Thus, a third-party or even connected plug-in can cause such a failure. Therefore, more often than not, you cannot understand what is wrong. Some things you can do:

  • when disconnecting a network connection. If you are behind a proxy server, for example, the plugin can wait a long time on the io network
  • you can check, for example, the resource monitor that launched eclipse. Some of the open file handlers may be related to the problem.
  • edit the .classpath file in the project where code completion ends and it will reset "your project stuff in eclipse
  • you can view the .metadata folder in the eclipse workspace, and you can guess which folder to delete on time. After uninstalling, try if the error is still present
  • create a new workspace and import projects into it
  • If the new workspace does not work, then eror is located in the configuration folder in the eclipse root, and you can play the same thing as in step 4
  • use brand new eclipse

+1 Perhaps some new plugin is responding. In the eclipse Help / about / installation / Installation history table, you can return to some older plugin sets.

Hope this helps.

+2
source share

It seems that you are encountering a known and already installed bug .

+1
source share

More articles:


All Articles