Closed heartacker closed 2 years ago
after hit format code action
reload window and than we could react with extension feature like git-lens
Which formatter extensions do you have installed? Does this reproduce when you disable all extensions?
It looks like the issue is caused by one of your installed extensions. All extensions execute together on a single nodejs process, so in order to narrow down the possible problematic extension, please try the following:
F1 > Help: Start Extension Bisect
initial | step | final |
---|---|---|
I have tried many times, and I cannot find the extension that causes this problem. because the issue is sporadic.
but actually, I have met this often;
Is there any other way to troubleshoot this problem?
When this happens do the following
UNRESPONSIVE extension host:
My suspicion is that an extension blocks the extension host process. When that happens automatic profiling should kick in and that should blame the extension responsible
I clear the windows output and reformat the json setting file, It takes long time and stop with this output
[2022-07-05 09:46:04.125] [renderer1] [warning] {}
[2022-07-05 09:47:05.808] [renderer1] [error] Cannot use 'in' operator to search for 'decimal' in undefined: TypeError: Cannot use 'in' operator to search for 'decimal' in undefined
at Object.provideHover (c:\Users\heartacker\.vscode\extensions\mateuszchudyk.hexinspector-1.3.0\out\extension.js:27:26)
at l.provideHover (d:\Users\heartacker\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:87:40222)
at d:\Users\heartacker\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:87:69849
at te._withAdapter (d:\Users\heartacker\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:87:66659)
at te.$provideHover (d:\Users\heartacker\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:87:69825)
at s._doInvokeHandler (d:\Users\heartacker\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:95:13708)
at s._invokeHandler (d:\Users\heartacker\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:95:13390)
at s._receiveRequest (d:\Users\heartacker\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:95:12107)
at s._receiveOneMessage (d:\Users\heartacker\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:95:10853)
at d:\Users\heartacker\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:95:8957
at w.invoke (d:\Users\heartacker\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:61:145)
at v.deliver (d:\Users\heartacker\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:61:2266)
at p.fire (d:\Users\heartacker\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:61:1844)
at a.fire (d:\Users\heartacker\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:69:18976)
at d:\Users\heartacker\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:111:34679
at w.invoke (d:\Users\heartacker\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:61:145)
at v.deliver (d:\Users\heartacker\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:61:2266)
at p.fire (d:\Users\heartacker\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:61:1844)
at a.fire (d:\Users\heartacker\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:69:18976)
at MessagePortMain.<anonymous> (d:\Users\heartacker\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:111:32714)
at MessagePortMain.emit (node:events:390:28)
at MessagePortMain.emit (node:domain:475:12)
at Object.MessagePortMain._internalPort.emit (node:electron/js2c/utility_node_init:5:364)
Please disable mateuszchudyk.hexinspector-1.3.0
and try again
no, that is not,
And I believe the vscode.git is the culprit
so many times, I have met other unresponsive case, and I see the git view always running.
and now I meet the same unresponsive case when I use git.sync with auto stash
THE IS NO END. AND ALL I HAVE TO DO IS RELOAD WINDOW AS mentioned earlier, that is the same problem phenomenon
And I believe the vscode.git is the culprit
Maybe, please disable vscode.git
and try again
I had tried to disable vsode.git, and we could not meet the problem anymore
We cannot save file sometime while git seems running
it takes a long time to save. and we notice that if the file was saved, and the git would stop runing the blue-process-line
Hey @jrieken, this issue might need further attention.
@heartacker, you can help us out by closing this issue if the problem no longer exists, or adding more information.
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!
Does this issue occur when all extensions are disabled?: I don't know because it is random
版本: 1.68.1 (system setup) 提交: 30d9c6cd9483b2cc586687151bcbcd635f373630 日期: 2022-06-14T12:48:58.283Z Electron: 17.4.7 Chromium: 98.0.4758.141 Node.js: 16.13.0 V8: 9.8.177.13-electron.0 OS: Windows_NT x64 10.0.25140
Steps to Reproduce:
json etc
other scenario:
I've had this problem so many times, it seems random