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
[bug] Windows: Sublime freezes and is impossible to kill it after you modify large number of files outside of Sublime #1582
Comments
I set I did notice that if I double click an answer button, then occasionally somehow ST would stop showing the message boxes until I click in ST again. (I'm also using Win 7 x64 BTW.) |
Yes, I had two ST windows open, though the second one was on another screen, so I forgot about it! |
Could you try to reproduce with build 3131? |
I'd be curious if you still run into this issue with build 3139. Not only was the sidebar rewritten in 3127, but in 3139 we shipped some enhancements to the filesystem notification handling on Windows. The issue in #1443 was a macOS internal change that altered how windows were raised to the front and caused a deadlock, so it wound up being something that would not cause issues cross-platform. @jakub-g Are you running the x64 version of Windows 7? |
Hi @wbond, yeah I run Win7 x64. I'll try to check soon with new Sublime but now I'm having a bit busy week. |
Closing due to no response. |
Summary
When you modify outside of Sublime a large number of files that were opened and modified but unsaved in Sublime, the editor freezes, and it's impossible to kill it with Task Manager, Sysinternals Process Explorer, or
taskkill /f
.You can see in Task Manager that Sublimes takes 12% of CPU (i.e. 1 full core on my 8 CPU machine).
Environment
Windows 7, Sublime 3 build 3126 (was happening also in a slightly older build)
Steps to reproduce
I had ~40 files opened, ~25 of them are localization JSONs (in many multiple languages, including Thai,
Arabic, etc. not sure how relevant this is but maybe it is)
The files had changes that I did manually, but those changes were unsaved.
Then, by mistake, I ran a bash script that modified those 25 files outside of Sublime.
When I went back to Sublime it started asking me for each file if I want to reload it or not.
But after several answers, Sublime becomes non-responsive. It's impossible to kill it via
taskkill /f
. The only way is to try to log off and have Windows kill it.I tried rebooting Windows and Sublime many times but every time result was the same.
Workaround
I had to delete
Auto Save Session.sublime_session
to get rid of the problem. The file was 360kB before deleting.The text was updated successfully, but these errors were encountered: