Community
Participate
Working Groups
All of a sudden, after having used this version of eclipse for several weeks, my run/debug configurations fail to open for any project. Either clicking on menu > run..., menu > run configurations, right mouse > run configurations, right mouse > debug configurations, right mouse > maven build... doesn't help. Nothing at all happens, the appropriate windows just don't open. Restarting the system sometimes solves the problem (but often not). trying to open the error log window from eclipse (show view > error log) keeps the error log window in an eternal "loading..." state without anything happening. Eclipse version: Eclipse IDE for Java Developers Version: 2020-03 (4.15.0) Build id: 20200313-1211 OS: Ubuntu 20.04 LTS.
Sounds lile a general issue with you IDE. Please attach the .log file you can find in the <workspace>/.metadata directory.
Created attachment 285248 [details] log file for eclipse
Hi all, sorry for not updating on this for so long. The summer holidays came in between, and then the problem disappeared by itself, so I forgot about it. But now it's back for a full blow, and I'm hardly ever able to get a run/debug window open. Most of the time, nothing at all happens when trying to open the run/debug window (via the main menu or the project's context menu). Sometimes the run/debug window opens, but then all my saved and recent run/debug configurations have disappeared, and it is not possible to create a new one (context menu > new configuration doesn't react to anything at all)). So all in all it's impossible to do anything useful with the opened window. When the run/debug window does open, this is sometimes (but not always) preceded by a dialog box which shows up a few seconds after having started eclipse. This box says: "'compute launch button tooltip' has encounted a problem. An internal error occurred during 'Compute launch button tooltip'. Could not initialize class org.eclipse.debug.internal.core.LaunchConfigurationInfo"
It seems the launch files were corrupted; however, with a text file they were readable and I could not detect any damage. When I deleted all launch files the problem described was gone.
Some more info after some additional research: it seems something goes wrong when saving a run configuration automatically when doing a JUnit test. I have 4 different workspaces with projects on my desktop PC. All these 4 workspaces have the same problem. That means that is not just some random file location on disk having gone corrupted. All problems are solved when I delete the JUnit-created launches. The launches which I created manually by myself are never the problem. So apparantly JUnit created run configurations can get corrupted while writing them, causing the launch configuration window not opening anymore.
@Noopur, Have you observed this with any JUnit test launches?
@Sarika: nope, the behaviour is rather random. I will try and get some more specifics on this. I'm not even sure if it is the JUnit launches. I generally have 10+ JUnit launches and 2 or 3 self-made launches, so the possibility exists that it is just coincidence that it appeared only with the JUnit launches and not with the others. Whichever launches are involved, the behaviour that existing launches cause problems in now rather consistent.
I haven't come across any bug report with this issue yet.
Eventually I think I managed to find the cause for this behaviour: It happens whenever I first opened an xml file in eclipse with the oxygen xml editor plugin, at any time in the session. After that, run/debug dialogs refuse to open. When I restart eclipse, the problem is usually solved.
(In reply to Rinke Hoekstra from comment #9) > Eventually I think I managed to find the cause for this behaviour: > It happens whenever I first opened an xml file in eclipse with the oxygen > xml editor plugin, at any time in the session. > > After that, run/debug dialogs refuse to open. > > When I restart eclipse, the problem is usually solved. Can you compare, if the editor makes any change ? Or may be the lock on the launch file is not released by oxygen xml editor.
@Sarika: > Can you compare, if the editor makes any change ? > Or may be the lock on the launch file is not released by oxygen xml editor. First question: You mean if it matters if I do make any changes to the xml file via the oxygen xml editor plugin? No, that doesn't matter. Just opening an xml file in eclipse with the oxygen xml editor plugin is enough to prevent the run dialog from opening Second question: I'd like to check that, but sorry you'd have to be a bit more specific on that and provide some guidelines. What launch file should I check, what's the exact name, and where can I find that? best, Rinke
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
