martinlippert
commented
6 years ago This is caused by the Spring tooling creating the beans model, which seems to take quite a while here. And the UI waits for that, which looks like a deadlock. That sucks.
As a workaround, you can avoid this by telling the Spring tooling not to create the beans model at all. You might loose some features (like auto completion in spring xml config files, the autowired hyperlink navigation, etc), but it would at least avoid the dramatic slowdown. You can go to the properties of your project, select the Spring section, and remove the spring config files that you have listed there. They are telling the tooling from which starting points the internal beans model should be created. And if there are no starting points defined, no beans model would be created... :-)
If you decide to do that, take care to also switch off the automatic config detection mechanism, otherwise your config files will automatically come back again... ;-)
This thread dump got reported here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=530450
It looks like the autowired hyperlink detector blocks the UI because it is waiting for the beans model to be created. It is not a real deadlock, but it looks like the bean model creation takes a very long time and this should by no means not block the UI.
We should change this and have something like a timeout when the autowired hyperlink detector tries to read the beans model.