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

Looking for an old network connection that has been removed #6475

Open
EpsOmega opened this issue Sep 7, 2024 · 4 comments
Open

Looking for an old network connection that has been removed #6475

EpsOmega opened this issue Sep 7, 2024 · 4 comments

Comments

@EpsOmega
Copy link

EpsOmega commented Sep 7, 2024

Description of the bug

Hello,

So if I am saving files via a VPN and then the VPN connection closes ( I close it or the lease expired ) if I still have the document open and I want to save it locally I have to wait maybe 3 mins or more.

Steps to reproduce

  1. Have a document open and save it to a network drive that is located at a remote location with the connection being a VPN connection.
  2. End the VPN session on purpose.
  3. Continue making changes to the document and then I want to save it locally for later when I reconnect to the VPN.
  4. At this point Sublime is waiting for a VPN connection that was ended, and it takes a long time to figure out the connection is gone.

Expected behavior

Sublime checks for the connection to the drive and after a few seconds, says, "I can't find the VPN drive, do you wish to save it locally? Yes or No keep waiting.

I choose Yes save it locally and I am done.

Actual behavior

I get the spinner going on for at least 3 minutes and have to wait.

Sublime Text build number

Latest version as of 9/6/2024

Operating system & version

Win 11

(Linux) Desktop environment and/or window manager

No response

Additional information

No response

OpenGL context information

No response

@BenjaminSchaaf
Copy link
Member

To clarify, where is the spinner happening? Is it inside the save file dialog?

@EpsOmega
Copy link
Author

EpsOmega commented Sep 8, 2024 via email

@EpsOmega
Copy link
Author

EpsOmega commented Sep 8, 2024 via email

@deathaxe
Copy link
Collaborator

deathaxe commented Sep 8, 2024

If an application accesses a file path, underlying OS starts taking action to provide requested information. Even a simple "do you still exist" request may trigger a network re-connection operation. The timeout is specified on OS level.

Depending on mechanisms network resources are mounted, it may be impossible for an application to detect them as such. Thus strategies to avoid such situations may be limited.

If for instance the OS native open/save dialog starts causing a hang, it's clearly an issue on OS level. I already often saw it hanging completely while waking up hard disks. That may also happen on network shares, while it tries to re-establish connections.

Normal TCP connections timeout in 10 or 30s normally. That's the time an application doesn't get any respond and has to wait.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants