Sublime prevents ejecting USB drive even after closing file

[woodrowbarlow]

Description

I posted on the forum and was asked to open an issue here.

If I open a file from a USB drive, edit it, save it, and close the file, I am unable to eject the USB drive until I close Sublime entirely.

Steps to reproduce

1. Insert a USB drive with a text file on it.
2. Open the text file in Sublime Text. Make a change and save the file.
3. Close the text file, but keep Sublime Text open.

(My setup has a "project" unrelated to the files on the USB drive, so I do have a file tree in the sidebar but none of these files come from the USB drive.)

Expected behavior

I expect to be able to eject the USB drive.

Actual behavior

When I attempt to eject the USB drive, windows reports "USB Drive (D:) is currently in use" and refuses to eject. If I close Sublime entirely, the drive ejects without complaint.

Environment

• Build: 3184 (Sublime Text 3 dev channel)
• Windows 10 Enterprise (x64), version 1803, build 17134.407

[keith-hall]

related:

• Deleting folders from sidebar fails if files in a sub directory were open #2403
• Unlock the project directory after closing the project on it #2288

[ncflagg]

Me too.
3.1.1 Build 3176
Windows 10 x64 version 1703

[wbond]

This has been fixed in build 3189

[tuck182]

This is still happening on:

Build 3207
macOS Sierra

Would you prefer I open a new issue?

Note: closing Sublime Text isn't required; it's sufficient to simply open a different file that's not on the USB volume. As an example:

$ diskutil umount /dev/disk2s1
Volume boot on disk2s1 failed to unmount: dissented by PID=26414 (/Applications/Sublime Text.app/Contents/MacOS/plugin_host)
$ subl /etc/hosts
$ diskutil umount /dev/disk2s1
Volume boot on disk2s1 unmounted

[FichteFoll]

Would you prefer I open a new issue?

Please do.

Also please include more precise steps for reproduction, e.g. whether ST was already running at the time you opened a file on the detachable storage and whether you can reproduce it in a clean state.

[tuck182]

Following up on this: a clean install of Sublime does not exhibit this behavior, so presumably it involves a plugin I'm using. I'll attempt to isolate which one before opening a new ticket.