I have this problem with my VS code(V1.43.2). I keep getting this error 'Extension host terminated unexpectedly.' When I open the developer tools to see where the error is I see these below errors
ERR Language client is not ready yet: Error: Language client is not ready yet
at t.LanguageClient.sendRequest (c:\Users\cc612417\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\html-language-features\client\dist\htmlMain.js:1:42925)
the other errors I see are
abstractExtensionService.ts:155 Extension host terminated unexpectedly. Code: 0 Signal: null
notificationsAlerts.ts:40 Extension host terminated unexpectedly.
I have tried disabling all the extension, I even uninstalled all the extension just to be sure but the error persists. Even when I opened VS code with parameter that disables all the extension --disable-extensions, the error persists. This error causes a lot of VS code features not to work, like code formatting, source control integration etc., I have tried updating it to the latest version as well.
Could you please help with this ?
Related
Request textDocument/codeAction failed.
Message: Internal error, please look at the server's logs.
Code: -32603
eveytime when i click README.md file, I always cathch this error at the terminal
i have checked the Markdown server, there was no something wrong.
I just had the same error and was caused by this extension "LanguageTool Linter". After uninstalling it (disable would probably work also) it stopped giving errors.
VScode Error message
[18:33:55.749] Resolver error: TypeError: Cannot read properties of undefined (reading 'replace')
at Object.a [as sanitizeConnectionToken] (/Users/username/.vscode/extensions/ms-vscode-remote.remote-ssh-0.84.0/out/extension.js:1:691806)
at Object.C [as findRunningServer] (/Users/username/.vscode/extensions/ms-vscode-remote.remote-ssh-0.84.0/out/extension.js:1:626542)
at async /Users/username/.vscode/extensions/ms-vscode-remote.remote-ssh-0.84.0/out/extension.js:1:622510
at async T (/Users/username/.vscode/extensions/ms-vscode-remote.remote-ssh-0.84.0/out/extension.js:1:619351)
at async Object.t.resolveWithLocalServer (/Users/username/.vscode/extensions/ms-vscode-remote.remote-ssh-0.84.0/out/extension.js:1:622460)
at async Object.t.resolve (/Users/username/.vscode/extensions/ms-vscode-remote.remote-ssh-0.84.0/out/extension.js:1:644834)
at async /Users/username/.vscode/extensions/ms-vscode-remote.remote-ssh-0.84.0/out/extension.js:1:727082
[18:33:55.751] ------
How to reproduce
Keep the remote connection in VScode
AFK (away from keyboard)
When the connection naturally breaks, then retry to connect
The error message will occur.
I found that one solution is to remove VScode cache at
/Users/username/Library/Application\ Support/Code
But this is definitely not the right way, any one knows the root cause and how to solve it?
I was able to fix this problem by upgrading the remote SSH extension version to the pre-release version.
Unfortunately, upgrading the remote SSH extension version to the pre-release version did not help me. What helped me though is a suggestion mentioned by Lilei Zheng:
I enabled "Remote Server Listen On Socket" option and it worked good so far.
This option is located in the "Remote - SSH" Extension Settings. I enabled it and I never had such problems again.
My VSCode extension is causing the extension host to terminate unexpectedly (happens after waking the computer from sleep).
How can I debug this issue? There are no additional logs before or after the Extension host terminated unexpectedly. Code: 3221225477 Signal: null entry in the console and debugging with an exception breakpoint doesn't help either as the Extension Host is terminated.
Is there some setting or flag I can enable to get additional logging for crashes such as this?
It seems 3221225477 shown in HEX is 0xC0000005 which is a STATUS_ACCESS_VIOLATION code on Windows.
https://github.com/Microsoft/vscode/wiki/Native-Crash-Issues#windows
I've been using my SQL database initialization script for a while, but it seems that recently the database crashes in the middle of the execution and I don't know why, but here's some details:
I am running OrientDB on Ubuntu 14 Trusty x64 (via Vagrant)
It always seems to crash while the script attempts to create a UNIQUE_HASH_INDEX, but doesn't always crash at the same UNIQUE_HASH_INDEX instruction
The script creates a lot of vertices and edges, but for example, it will crash here (see line with UNIQUE_HASH_INDEX):
CREATE CLASS Channel EXTENDS V;
CREATE PROPERTY Channel.version LONG;
CREATE PROPERTY Channel.channelId STRING;
CREATE INDEX Channel.uq_channelId ON Channel(channelId) UNIQUE_HASH_INDEX;
The database crashes entirely with the following error:
Creating index... Error:
com.orientechnologies.orient.core.exception.OStorageException: Error
on executing command: sql.create INDEX Channel.uq_channelId ON
Channel(channelId) UNIQUE_HASH_INDEX
Error: java.io.EOFException
Looking at the log files, the only hint I get are the last two lines:
2016-01-14 17:17:05:437 INFO Received signal: SIGTERM [OSignalHandler]
2016-01-14 17:17:05:454 INFO Received signal: SIGTERM [OSignalHandler]
How can I resolve this issue, or at least get better hints as to what is making the database crash?
I also test with OrientDB 2.1.6, as I was running the older version initially. Same problem.
Sorry, false alarm -- this is a Vagrant issue, not an OrientDB issue. Running the exact same script on a 32bit instance instead of 64bit solved my problem, and installing the same script on a real 64bit server also works.
Sorry, not really programming question, but I am not sure where else I could find some help.
After a recent update (Xorg was updated among other things), GTK apps stopped running in my kde4. I have a Debian unstable, updated around 22 April. When I try to run them I get the following error:
ga#grzes:~$ iceweasel
The program 'firefox-bin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadName (named color or font does not exist)'.
(Details: serial 888 error_code 15 request_code 45 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
ga#grzes:~$ gimp The program 'gimp' received an X Window
System error.
This probably reflects a bug in the program.
The error was 'BadName (named color or font does not exist)'.
(Details: serial 6955 error_code 15 request_code 45 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
(script-fu:4643): LibGimpBase-WARNING **: script-fu: gimp_wire_read():
error
I have to restart the font server manually to have it fixed:
ga#grzes:~$ su
Password:
grzes:/home/ga# /etc/init.d/xfs restart
Stopping X font server: xfs.
Setting up X font server socket directory /tmp/.font-unix...done.
Starting X font server: xfs.
Any ideas what could be wrong? Is it a configuration issue? My system has been updated for the last 7 years, so I can have some old settings.
Debian unstable is very... unstable now, since a release was made a short time ago. Major changes and packages migrations are happening. Xorg (and all X related stuff) being one of the critical packages in that process. My advice is to perform a new update/upgrade in order to catch a new version that may resolve this problem.
It's very frequent that after an update some thing will get broken in inexplicable ways, simply because the developers are uploading new, and not much tested, version of the applications
I finally figured this out: seems like xfs is not compatible with the other components currently and luckily removing it form the system completely solves the problem.