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

VSCode 1.33 two main bugs on Ubuntu 18.04 #73303

Closed
francis-chang opened this issue May 5, 2019 · 6 comments
Closed

VSCode 1.33 two main bugs on Ubuntu 18.04 #73303

francis-chang opened this issue May 5, 2019 · 6 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s) freeze-slow-crash-leak VS Code crashing, performance, freeze and memory leak issues typescript Typescript support issues upstream Issue identified as 'upstream' component related (exists outside of VS Code)

Comments

@francis-chang
Copy link

Here are the bugs i've been noticing on Ubuntu 18.04 even despite disabling extensions and changing to default settings.

  1. Intellisense is EXTREMELY SLOW. for example, I will type 'hello' randomly in my typescript function and the red underline that should come up almost instantly takes nearly 7-8 seconds to see.
  2. Saving files has a weird behavior. When i save, it will, for one second, be saved, but then unsaved again. Repeating this process to save around 3-4x will do the trick.
  • VSCode Version: 1.33
  • OS Version: Ubuntu 18.04.2 LTS

Steps to Reproduce:

  1. Download Ubuntu 18.04.2 LTS
  2. Open a typescript file in VSCode 1.33

By the lack of open issues about this has me worried that i'm an extreme edge case and that it has to do more with my machin than vscode, but please still check it out. It's been bugging me since 1.32

Does this issue occur when all extensions are disabled?: Yes/No
Yes
I have to revert my code to version 1.31 to have these issues mitigated. I say mitigated because i'm still having the saving issue on 1.31, but the intellisense is what it should be.

@RMacfarlane
Copy link
Contributor

Hey @fc373745, can you also please make sure you have the latest version of @types/styled-components installed? See DefinitelyTyped/DefinitelyTyped#34391 for details, both of these issue may be caused by that

@francis-chang
Copy link
Author

seems to be the solution. thanks!

@francis-chang
Copy link
Author

francis-chang commented May 8, 2019

was fine for one day, but all of the sudden its broken with the same problems again
also typing console.log auto imports import console = require("console"); to my file.

I have reverted back to 1.31

@types/styled-components is in its latest version ( "@types/styled-components": "^4.1.14")

@francis-chang francis-chang reopened this May 8, 2019
@RMacfarlane RMacfarlane added the typescript Typescript support issues label May 8, 2019
@francis-chang
Copy link
Author

Sorry i didn't read thoroughly to the referenced issue, and upon further reading, i had to DOWNGRADE @types/styled-components to 4.5.1 which seems to solve it.

@francis-chang
Copy link
Author

After playing around with the versions of typescript, @types/styled-components, and vscode, i have gotten the bugs with any of the combination of these

code 1.34
typescript 3.4.5, 3.3.4000,
@types/styled-components 4.1.11, 4.1.12, 4.1.15

any version of code 1.34 has a problem with matching with any of these dependencies

For some reason upgrading, downgrading typescript or @types/styled-components serves as an initial solution, but after a couple of hours, it will start to break down again (weird saving behaviors, extremely slow intellisense and typescript linting/checking)

The best way i can mitigate this is to downgrade code to 1.31 and it actually has the best result.

here is what i'm using.

code 1.31
typescript 3.4.5
@types/styled-components 4.1.11 (the latest - 4.1.15 will give me problems even in code 1.31)

Really weird things happening, might give up styled-components and go back to css modules after this 😭

@mjbvz
Copy link
Collaborator

mjbvz commented May 22, 2019

Duplicate of microsoft/TypeScript#30819. Please try using the latest VS Code insiders build

@mjbvz mjbvz closed this as completed May 22, 2019
@mjbvz mjbvz added *duplicate Issue identified as a duplicate of another issue(s) freeze-slow-crash-leak VS Code crashing, performance, freeze and memory leak issues upstream Issue identified as 'upstream' component related (exists outside of VS Code) labels May 22, 2019
@vscodebot vscodebot bot locked and limited conversation to collaborators Jul 6, 2019
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) freeze-slow-crash-leak VS Code crashing, performance, freeze and memory leak issues typescript Typescript support issues upstream Issue identified as 'upstream' component related (exists outside of VS Code)
Projects
None yet
Development

No branches or pull requests

3 participants