Multiple instances of .ino open in IDE window

During programming today I noticed that I have 2 instances of the .ino file open. they show also the file location in the tab. I have no idea how it got there or how I can close it.
image
right-click on tab shows the option (empty)?
Restarting the IDE restores the session with 2 open instances.

Thanks for your report @Xinonix. This is a known bug that is being tracked by the Arduino IDE developers here:

One of the developers did some investigation on it today and found it is a problem with the Eclipse Theia IDE framework the Arduino IDE 2.x is built on:

There were some previous reports of this issue being triggered by other operations in the Arduino IDE:

Those issues were fixed in Arduino IDE 2.0.0-rc7, so at least it should be less likely to occur when using the latest version of the Arduino IDE even if not all the possible causes were fixed. If you are using an older version of the Arduino IDE 2.x, I recommend you to update to either 2.0.0-rc7 or even better to the latest nightly build:

https://github.com/arduino/arduino-ide#nightly-builds

This is unrelated. Since they were not relevant to Arduino's specific use case, the items that would normally appear under that context menu were removed by the developers, but they did not remove the context menu itself at that time. Hopefully the useless empty context menu can eventually be removed, but for now please just ignore it.

I am running the latest version, rc-7, so this might be a new one or an unsolved.
The right-click on tab did show (close-right) in this release, earlier and that resulted in closing the last tab. I could not repeat that action...

Is there a known way to close the second occurance of the .ino file?

Yes. Please follow these instructions:

  1. Open the "Command Palette".
    (Ctrl+Shift+P or Command+Shift+P by default)
  2. Run the "View: Reset Workbench Layout" command.

Gives me a
image
for the last 15 minutes...
Restart solves that one.

Thanks for reporting that. We have been tracking this sort of hang issue here:

Unfortunately, none of the team are able to reproduce the issue at the moment, which makes the investigation and development work to fix it extremely difficult. I do not experience this thing when I reproduce the steps you followed to reach it.

If anyone finds a procedure that can be followed to reliably reproduce the issue, please do share detailed instructions here. That would be very valuable in any efforts to fix this.

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.