editor becomes unresponsive all the time since last update

[preexo]

• VSCode Version:1.2.0
• OS Version:Windows 10

Steps to Reproduce:

1. Open Visual Studio Code
2. Update to latest version

I just updated my Visual Studio Code to the latest version. Congratulations, since then it is unresponsive all the time. I can work for a few seconds, then I hit a key, it freezes and can only be solved by killing the process through task manager...
It was running nice and smooth before the latest update, which I got today. Sadly I can't work like this and need a reliable editor, so I have to go back to use something else now.

Good luck.

[danielepolencic]

Since the last update, the editor is very slow for me too. I'm on Mac (10.10.5) and I just upgraded to 1.2.0

EDIT: I run VS Code vanilla. No plugins.

[doyint]

I am experiencing the same thing to plus saving the JS file the title are start to flicker and will not save.

[workingj]

I am experiencing the same thing if i open a third file-tab.
It also does not refresh the window if i (alt-tab) into an other open programm, like browser etc.
_ Edit: I work on Windows 7._

[calebegg]

I'm also seeing a lot of freezing with the latest update. I can generally only go ~10 minutes between freezes, and when it freezes all I can do is kill the whole process. Is there somewhere we can look for crash dumps/log files?

1.2.0 on Ubuntu 14.04; I almost exclusively use VSCode for TypeScript.

[alexdima]

I am sorry you are experiencing this. To help us reproduce, can you please give us more details. Is there a common pattern between these freezes (I see that they occur on Windows 10, Windows 7, Ubuntu and Mac), so I'm thinking they are not OS specific (if they have the same root cause).

What sort of languages are you working on? I see TypeScript and JavaScript mentioned. Is that true for everybody? We have had quite a few issues with the TS/JS grammars (sometimes they recurse to death). Is it possible that this happens when opening a certain file or a file containing a certain pattern that would cause the grammars to go crazy?

We would appreciate any other details to repro this.

[alexdima]

Are you using the new integrated terminal?

[calebegg]

Are you using the new integrated terminal?

I'm not.

We would appreciate any other details to repro this.

I tried it a bit more today, and, at least for me, it seems to always happen when I try to save. I press ctrl+S, but the save operation never completes (the black dot never goes away, and the file never actually gets saved). I then have to kill the process and try again. It happens maybe 5-10% of the time (or less) when I try to save (most save operations are successful and instant)

The files I'm editing are on a networked filesystem, which might be related, though I'm confident that that's not the direct cause, because (a) this has always worked in previous versions and (b) I'm not seeing this problem in other editors, including a 1.1 install of VS Code.

[doyint]

That's exactly the same thing for me, I think it might be .js file related because I have some html and php file open in different tabs and it never happened on those files, I initially thought it might be because the terminal was opened, but that wasn't the case, and I also thought it may be because their is a grunt watchify on the folders I am working on, but it's wasn't the case either, I have also started removing some plugins, which initially things seems fine, so I would attribute that to the plugin bug. But then I am still getting the same issue again.

Windows 7
I am on cooperate network.

I installed V1.1 to see if I could revert back but that problem still occurred.
I am back on v1.2

Temporary solution for now is:
After press CTRL + S to save, the flickering starts to happen, as if it's trying to save but then cant save which sends it's in a endless loop.
If I press CTRL + Z, to undo, it will stop and eventually save the file, the implication of that is, I lose the complete history of the file, so I can't further undo any actions, prior to me saving it.
Solution B: Sometimes I also find if the flickering is happening, if I switch to debug to view git file changes, then this also terminate the flickering and saves the file also. Again I still lose the file history meaning I can't undo any changes made prior.

It's a pain to work with now.

I hope this is enough information.

[preexo]

I am using VS code only for PHP programming. I could use it a few seconds, a couple of keystrokes and it would freeze and never wake up again.
I just gave it another try and just uninstalled, then reinstalled it. It seems fine for now.

Even though all users are describing similar symptoms, we all seem to use it a tiny bit different and therefore it might all be related to completely different problems.

Anyway, it works fine for me at the moment.

Is there no debug more with log files or anything that we could append the next time this happens?