Skip to content
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

"window.restoreWindows": "folders" doesn't work under Linux #49050

Closed
MrChriZ opened this issue May 2, 2018 · 9 comments
Closed

"window.restoreWindows": "folders" doesn't work under Linux #49050

MrChriZ opened this issue May 2, 2018 · 9 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s) info-needed Issue requires more information from poster workbench-state UI state across restarts

Comments

@MrChriZ
Copy link

MrChriZ commented May 2, 2018

  • VSCode Version:Version 1.22.2
  • OS Version:Linux Mint 18.3

Steps to Reproduce:

  1. Set "window.restoreWindows": "folders"
  2. Close Code
  3. Relaunch code
  4. Only one Window reopens.

Does this issue occur when all extensions are disabled?: Yes

@bpasero
Copy link
Member

bpasero commented May 3, 2018

@MrChriZ video proof please

@bpasero bpasero added the info-needed Issue requires more information from poster label May 3, 2018
@MrChriZ
Copy link
Author

MrChriZ commented May 3, 2018

OK Slightly different -- here's a video of it not working in Windows which is running under a VM on my Linux setup. It was easier to demonstrate code being closed unexpectedly here by killing the VM:

https://www.youtube.com/watch?v=NDwZtpLgOA0&feature=youtu.be

This is a clean install of code.

@MrChriZ
Copy link
Author

MrChriZ commented May 3, 2018

Something more nuanced is going on under Linux
I setup the Red and Blue folder test this time under Windows and code worked as expected.

I opened two Ember projects I'm working on and killed code and then reopened and it instead reopened my red / blue folders I had opened previously.

https://www.youtube.com/watch?v=Tc9AgbWlTSE&feature=youtu.be

@MrChriZ
Copy link
Author

MrChriZ commented May 3, 2018

It dawned on me that there may be some kind of timer which waits for a while before saving the folder set and so causing the results I'm seeing.
As such I've just retested the Windows system - this time leaving code with the red and blue folder set left open for 30 minutes prior to an unexpected system restart. Code still opened a different folder set than the one I had opened for 30 minutes prior to unexpected system restart.

Linux however is behaving more as expected with this method of testing however.. I'll keep working to see if I can reproduce my issues which are usually caused when the battery on my laptop runs out of juice prior to the operating system shutting down in an orderly fashion.

@MrChriZ
Copy link
Author

MrChriZ commented May 3, 2018

So I tried again opening two folders sets in Linux. I interacted with both flicking through different files.
I then left them for around 5 minutes. Prior to a restart which I video'd.
Now please excuse the shakey hand video - but I don't have a VM set up for Linux and I can't screen record a full system restart.

https://www.youtube.com/watch?v=jDS-DnSnP6A

Again Code does not open the correct folder set.
At the start of the video 0:06 in the top window I have my RedPill folder open.
When I reopen code 0:54 in the top window code reopens my EmberJS folder.
The bottom window I believe opened the correct folder... but opens with a different file.

@bpasero
Copy link
Member

bpasero commented May 3, 2018

@MrChriZ wait a sec, you "power off" the machine while VS Code is running and expect it to restore all windows then? I think there is a high likelyhood that this kills VS Code without having a chance to persist any data. VS Code needs a normal shutdown for this feature to work.

Can you please reproduce this issue by opening 2 folders, then selecting File > Quit and then starting again?

@MrChriZ
Copy link
Author

MrChriZ commented May 3, 2018

"VS Code needs a normal shutdown for this feature to work."
Why? Chrome manages to remember which tabs I had opened in a similar setup.
Android Studio returns to exactly the state you last used it in.

It can't be that hard to remember which folders were last opened (at the point they were opened)?

@bpasero bpasero added the workbench-state UI state across restarts label May 4, 2018
@bpasero
Copy link
Member

bpasero commented May 4, 2018

Yeah agreed, so marking as duplicate of #12058

@bpasero bpasero closed this as completed May 4, 2018
@bpasero bpasero added the *duplicate Issue identified as a duplicate of another issue(s) label May 4, 2018
@MrChriZ
Copy link
Author

MrChriZ commented May 4, 2018

Thanks did search but didn't see that one.

@vscodebot vscodebot bot locked and limited conversation to collaborators Jun 18, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s) info-needed Issue requires more information from poster workbench-state UI state across restarts
Projects
None yet
Development

No branches or pull requests

3 participants