Running vscode 1.66.2 on mac Monterey 12.3.1. It's been working fine, but after a reboot it suddenly won't find any of my installed plugins/kernels. When I try to run a python file it points me to the marketplace, saying I don't have an extension for debugging python. However, when I follow that link it shows it's installed...does anyone know what might be going on?
Related
Good day community. I have installed VS Code in my MacBook Air M1 chip running on BigSur 11.3.1 but whenever I set the code command in PATH (using Command+Shift+P) it only appears to be working for current session and doesn't work if I restart VSCode. I have to set the code command in PATH again. Please help me in configuring code command permanently so that i can open VSCode from any directory whenever I want. Thanks
I think I have got the solution. After installing VSCode in your Mac (which will be in download folder) move VS Studio Code.app file to Application Folder and then again install the code command in PATH from VSCode(using Command+Shift+P) and thats it.
I have tried uninstalling and reinstalling it, but the problem did not dissappear. It seems that when I open the app, more than 20 windows open at the same time, causing the app to crash. Here is a screenshot:
I've searched on the internet for what else to do, but I didn't come across any solution.
The solution was to start VS Code from the command prompt with the following command:
code --disable-extensions --max-memory=12288mb
Then to close all open tabs and correctly exit VS Code without any open files.
Hopefully this helps someone!
I tried all the fixes above when my Ubuntu install of VS Code crashed repeatedly at startup. The only thing that worked for me was deleting the entire ~/.config/Code/Backups folder. Back it up first, just in case!
I had the same issue with the latest version of VSCODE. Then i tried installing "Downloads: Windows: User" one from https://code.visualstudio.com/updates/v1_52. It worked. I am not sure of the root cause.
I observed that after installing the extension 'Django Template Support' the VSCode started crashing.
I tried by installing the latest version of VSCode too. Still the VSCode did crash.
Once after uninstalling that extension, VSCode is working fine.
May be, we should note the change which has made the VScode to crash (though, it shouldn't, I believe.)
I installed and configured the Apollo GraphQL extension in VSCode. It worked perfectly.
However, when I close and reopen VSCode it doesn't load. The icon never shows up and nothing loads in the console output.
The extension is definitely loaded because syntax highlighting still works but we get none of scheme features.
I tried
uninstall/reinstall of the extension.
closing vscode, deleting the extension folder directly, reinstall extension, restart vscode.
installing the Insiders Edition of vscode and installing the extension there.
In all cases it works the first time but not after a restart.
How can I troubleshoot/fix this issue?
I am running into an issue with Visual Studio code where i could not able to launch it in Windows 8.1. It is working fine untill few days back. Even though it shows two processes named Code 32 bit are running in Task Manager, i cannot see the VSCode UI. I tried going to folder and right click and click on Open with Code, but no luck.
Even after uninstall and installing the VSCode also, i am running into same issue. Does anyone face this issue before?
Is there a way i can clean uninstall VSCode and re install?
Thanks,
Phani
Did you try AppData\Local\Code\bin\code.cmd ?
vscode is running by update.exe
I am using nsight eclipse edition for mac to debug my cuda code. I was able to run cuda-gdb all fine from a terminal but was not able to use the debug function in Nsight. Whenever I started to debug, an error window pops up saying "Error in final launch sequence
Connection is shut down". My OS is Mac Lion (10.7.4).
I understand the big thing in Cuda 5.0 is the interactive debugging with eclipse but sadly I won't be able to use it unless I switch to Windows or Linux. If anybody has seen this or knows a workaround for this, please let me know and your help will be very much appreciated.
Thank you!
I'm afraid you've hit a known issue in CUDA 5.0 Toolkit. Due to some last-minute change, cuda-gdb (which is a shell script) is not entirely valid in Mac OS X. To remedy the problem:
Edit cuda-gdb shell script.
Make line #!/bin/sh the first line in this script.
Save the changes
We apologize for inconvenience. This (and many other) issues will be fixed in the upcoming CUDA 5.0 RC release.
I had this problem in linux recently.
Error in final launch sequence Connection is shut down which means nsight can not start debugger correctly.
first you have to make sure you can run cuda-gdb in terminal. just type cuda-gdb in terminal, if it says like cuda-gdb cannot find some lib in /usr/lib, just download or relink it. after you done this , rerun cuda-gdb in terminal, it should work fine. then you can use nsight debugging tool.