New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Subclipse causes Eclipse 4.20 to get SWTException at startup after unclean shutdown #188
Comments
Unfortunately there is no one that regularly contributes to this product any more :( If someone submits a PR I always try to find the time to get it merged and I did manage to get everything automated so that PR's and merges publish builds so it is easy to try them out. FWIW, Eclipse 4.20 still works fine for me. I guess that is good news in terms of the scope of the problem and the people affected but it does make it more difficult to know if a PR really fixes the problem. |
Yes, Subclipse works fine with Eclipse 4.20 as long as it shuts down properly. If it is halted e.g. due to JVM termination, you get this bug all the time when you restart Eclipse. I know that some files could be deleted in the .metadata/.plugins directory to cure the workspace refresh, but I can't seem to make that work. Do you know what files they were? Otherwise, the only way to fix it is to delete the .metadata directory and re-import all existing projects again. This is a sad thing when you have tons of projects... |
Thanks, if someone ever submits a PR, I will try killing my Eclipse process to see if I can recreate the problem and then try again using the PR. |
I have just tried Eclipse 4.21.0 (2021-09) on an Ubuntu Linux 20.04 and using OpenJDK 11.0.11. I'm not sure, but I think the situation got worse. On a fresh installation and fresh workspace, immediately after installing Subclipse 4.3.3 (via the Eclipse Marketplace), Eclipse hangs/freezes after startup. More precisely, the startup procedure seems finished but as soon as I click on any menu item, the UI freezes. This is very likely caused by Subclipse, since it is the only plugin that was added to the fresh installation and workspace, which was even completely empty (i.e. no projects existed). |
This bug was reported in Eclipse 4.20, but it looks like it's Subclipse causing the problem. If performing the same thing as described in Bug ID 574552, see comments no 9 and no 10 in the bug Eclipse report 574552.
The problem is that SVNUIPlugin.start causes Display creation in Eclipse when creating images in non-SWT thread ("Worker-1 Refreshing workspace"), you can see it in the stacks for first and second call to Display constructor in attached file bug574552-Display-constructor-stacks.txt.
When Subclipse is removed from the Eclipse 4.20 installation, attempting to reproduce the error seems not to be possible as described in comment no 9.
The text was updated successfully, but these errors were encountered: