_From @andreasgruenh on April 5, 2018 16:35_
Steps to Reproduce:
{}import React from 'react';After looping 3-6 times, the error occurs and Intellisense and hover information are broken and will only come back when the tsserver is restarted.
Does this issue occur when all extensions are disabled?: Yes
I uploaded the log when this occured here: https://gist.github.com/andreasgruenh/95dfe15dd23d3dfdb547db088199fdbd
Here is a gif of the reproduction: https://gfycat.com/LavishMasculineDuckbillplatypus
The Window has been reloaded directly before the start of the gif and the bug occurs after the 4th file has been created.
_Copied from original issue: Microsoft/vscode#47248_
Moving over to typescript repo for better visibility.
I see a Error: No Project. exception in the logs but am not sure if this is a symptom of the problem or could be the cause. There also seems to be a weird c:/jsconfig.json project being created
@andreasgruenh Can you please test this using the just released VS Code 1.22 as well
From the log it looks like the getErr is sent after closing the script info. So the throw no project seems correct
Thanks for the quick response!
The error is still happening in 1.22.1 (this time after the second created file (b.js)).
Recreated it with the newest version and --disable-extensions. Here are the logs: https://gist.github.com/andreasgruenh/c6c9a87131de87e60ed756f00c2ac881
![]()
I'm seeing some weird (at least to me) occurrences of /dev/null starting in line 4355 after the b.js file has been created:
Info 918 [8:6:28.9] Starting updateGraphWorker: Project: /dev/null/inferredProject1*
...
Info 936 [8:6:28.419] Scheduling request for: /dev/null/inferredProject1*
Info 937 [8:6:28.419] Starting updateGraphWorker: Project: /dev/null/inferredProject1*
Info 938 [8:6:28.422] Finishing updateGraphWorker: Project: /dev/null/inferredProject1* Version: 2 structureChanged: false Elapsed: 3ms
Info 939 [8:6:28.423] remove project: c:/Entwicklung/vscode-bug/src/App.js,c:/Entwicklung/vscode-bug/src/App.test.js,c:/Entwicklung/vscode-bug/src/index.js,c:/Entwicklung/vscode-bug/src/registerServiceWorker.js,c:/Entwicklung/vscode-bug/src/a.js
I'm not seeing anything out of the ordinary in my logs, but this time intellisense is completely broken.
It was bad that it stopped after a while in the previous build, but now, right from the start, it doesn't have any suggestions for anything, with or without extensions enabled.
Happens for me too, really annoying...
@andreasgruenh in https://gist.github.com/andreasgruenh/c6c9a87131de87e60ed756f00c2ac881 there is no Info 939 or anything beyond Info 759
@sheetalkamat Gists only show the first x thousand lines. Press on raw in the top right corner (at least on desktop) to see the full log file. (The first logfile also gets truncated by Github).
The second log file has info lines until Info 1465.
Should I post logs via a different channel?
@andreasgruenh Thanks, I got the logs. Will take a look.
@andreasgruenh can you please try out the next drop that gets release tonight to see if it helps with the issue. Thanks.
that is typescript@next published tomorrow. [email protected] to be exact.
@sheetalkamat Your fix seems to work for me! Thank you so much for reacting so quickly!
Will this be merged into a 2.8.x release aswell or will it only be in 2.9?
Should be in 2.8.2 as well
me to, im using react native for my vscode, after 2 minutes - 10 minutes always infinite loading my intellisense vscode,
please fix this
vscode 1.22.2 fixed all the issues I was having.
what your problem, before your update to vscode 1.22.2?
@mikevaleriano
@byteskw Intellisense would stop working after a few minutes. That was when 1..21 came out in February.
It was tolerable, but I had to use the Reload Window command often. Then 1.22 came in early March (it probably was 1.22.0) and Intellisense was completely broken out of the box - it wouldn't work with the TypeScript version it came with, or any other you could install elsewhere.
1.22.1 came a few days later without a proper solution, and I actually started looking back at atom for a while, but 1.22.2 was released a couple days ago and everything seems fixed.
I'm using the TypsScript version that comes with it, 2.8.1. And this leads me to believe there was never a problem with TypeScript to begin with, and it was a vscode issue that they finally handled.
@mikevaleriano These problems still occur to me on vscode 1.22.2. With TS 2.9, they seem to be fixed. The error on the TypeScript side should be fixed with TS 2.8.2 as @mhegazy said, so I'm waiting patiently for that one.