I didn't find an answer to this problem with nodejs:
I have a breakpoint in index.js at the line require("./test). When I click the Step Into button, the debugger doesn't jump to the test file like it should, but instead runs and displays the result immediately. I don't have any expressions for watching.
P.S https://github.com/microsoft/vscode/issues/15253 - this issue from github is the same as mine
Kind regards
I found the problem ,tried to reproduce on my personal laptop and the debugger was worked fine(node v18.14.0). On my work laptop node version were 19.16.0.I switched to 18.14.0 and the debugger starts work as expected.
Related
I've been trying to run a code in my laptop but all of a sudden this message shows up.
The thing here is that I'm reading a file with 105232 lines, and at line 94559 it shows this error. I already tested this code in another PC and it works fine. I don't know if it happens because of memory usage or what, i've already tried changing some settings but it still doesn't work. I tested other projects I got in here and they work just fine.
Yesterday, VSCode (1.67.1) decided that it was unable to start (crashes immediately) and spits out the error code -1073741818. I have the option to reopen or close but nothing happens regardless of the option chosen. Thought it might be an issue with the file/folder I was opening but no success opening any files/folders at all. Tried to disable GPU, disable extensions and re-install but all lead to the same error code. Tried to move to Atom, but, oddly enough, the same issue occurred. Discovered Atom and VSCode are both based on Electron and that Electron has previously had issues with Nvidia drivers (currently running 512.77) so I tried to install previous versions of the drivers that were working but no success. I finally gave up and moved the code to another system and everything works flawlessly.
So now I that I have some time, I am trying to figure out what went wrong and where to go from here. My uninformed, uneducated guess is it is driver related but I am not sure how to resolve it. I was able to successfully use VSCode earlier in the day with no issue. The system went into stand-by mode and upon return, the issue began. Any suggestions/guidance on where to start would be greatly appreciated.
VSCode Crash Window
Welcome to the community! I think this is caused by an corrupt installation of vscode, try to restart your computer and maybe reinstall vscode by going to, https://code.visualstudio.com.
If that does not help maybe try to submit an issue on the vscode github here: https://github.com/microsoft/vscode.
How to submit an issue on github:
Find the menu bar where it has multiple menus, it should have: "code", "pull requests" and "issues".
Click on "issues" button.
Click "new issue" to create an issue.
Then click "bug report" and enter details to file issue.
Once ready click submit issue to submit your issue in github.
Also, you'll need a github account to create a issue, signup here: https://github.com/
I hope this helps!
Please check if you've installed any additional extensions which may be causing the VSCode to crash.
My VS code keeps crashing when opening it
I had the same problem. First, it used to crash once every 10 minutes, then it started crashing 10 times a minute after a few hours. It just stopped working that day.
I don't know how it was resolved but it did automatically resolve.
I searched for the solution but the VS code on GitHub was already closed. If applicable take a rest and let your PC calm down also. Then if the problem doesn't get resolved, try contacting the developer team.
I'm running the vscode 1.64.2 on Windows 10. Currently i met a strange problem, When i resize the terminal in the vscode and the cursor is focus on the terminal, Then it will trigger ctrl+c . At this time any running command would be terminated immediately .
To avoid this i have to un-focus for the terminal first and then resize it. Any suggestion here?
I was searching about this with no luck. Today I realized about one installed software on my machine that has a global hook on mouse selection. In my case was the QTranslate software. When I exit the application the problem was solved.
Check if you have this or another software that has a global hook on mouse selection.
In VS Code this problem (control C) was happening for any command line inside the terminal. Apart from that, opening Git bash (standalone) I was having the same issue, but not for cmd or another command line.
Hope this helps you because this was driving me crazy.
Absolutely working solution!
I experienced the same problem with mouse strange behavior for a long time, but finally I found out it was the QTranslate's guilt! After I stopped it, the problem has gone. (can't vote up because of my virgin profile here).
PS: I found the solution how to push work both QTranslate and terminal window - just set QTranslate setting "Advanced->Copy action" to "Ctrl+Insert" instead of Ctrl+C.
So I have been using VS Code for a while now, and as of recently when I start up the program, within a couple minutes, my entire computer freezes. I have attempted re-installing it. I have made sure im on the latest update, and I have not recently installed any extensions in the days leading up to this issue.
It is consistently freezing though. Even after restarting my computer and re-installing the application. I have no clue what could be causing this but I really do enjoy VS Code and would like to not have to swap to something else.
Any help is of course greatly apprecaited. Thanks!
I got the same issue in my Ubuntu 16.04.
I did switch off git.autorefresh in the Settings, then it works flawlessly and smoothly
If the problem keeps occurring, I guess an extension is causing the issue (must be).
Try to remove the extensions one by one or disable it in settings then test again. I got the same issue and its fixed after removing the git blame extension.
I had the same problem and adding these settings to Visual Studio Code the PC freezing doesn't happen anymore:
Open VS Code settings (press F1 -> "Preferences: Open Settings
(JSON)";
Add these json properties at the end of your settings
"search.searchOnType": true,
"search.followSymlinks": false,
"search.collapseResults": "auto",
"search.maxResults": 2000,
Save settings.
It freezes a lot too
if you check task manager without vs code it should okay but after you open vs code and try it its the disk has like 100% or something that's why it's freezing
What I'm doing
I am using the instructions on this page to generate a Hello World extension for Visual Studio Code. I've generated the extension using Yeoman and am now simply trying to launch the hello world extension in an Extension Host instance of VSCode using the debugger by hitting F5.
The problem
I am receiving a notification at the top of the original VSCode window that reads, "Error cannot connect to runtime process (timeout after 3000ms) launch.json | Close".
This error appears slightly before the Extension Host window opens.
Once the extension host window opens, it spins a bit and then shows this warning at the top of its window:
The warning reads, "warn plugin host did not start in 10 seconds, it might be stopped on the first line and needs a debugger to continue | Close".
Seems like I just need some way of making the runtime timeout longer but I haven't found out how to do this.
My environment:
OSX 10.10.5 Yosemite
Node 0.12.7 or 4.2.1 (I've tried both)
Visual Studio Code 0.10.1
EDIT: This only happens when using Typescript in the Yeoman generator. I tried the Javascript version and it works fine.
Given that this seems to be a bug, I've opened this Github issue with the code yeoman generator.
It's simple but I spent 1 hour to find the issue.
I think mistake I did is first I created launch json and installed chrome debugger and then I modified launch.json for chrome launch so did not work.
So I tried below and it worked.
Deleted launch.json and reinstalled chrome debugger extension and
restart visual studio code and create lanch.json after these steps it worked :)
Try it may work.
This happens to me as well. I simply reload the extension by pressing F5 again and it usually works. Rarely it will fail twice in a row and then will work on the third time.
Not really a "solution" to the problem, but it's worked so far.
Find %VSCodeHome%\resources\app\extensions\node-debug\out\node\nodeDebug.js and change wait time in line 203.
// try to attach
setTimeout(function () {
_this._attach(response, port, 3000);
}, 2000);
into time working for you, like:
// try to attach
setTimeout(function () {
_this._attach(response, port, 10000);
}, 2000);
Worked for me.
Accessing the Internet through a proxy may also cause this. It's due to the source map downloader doesn't use your proxy, so the download always times out after attempting to connect for a long time.
For those who encounter this, try the workaround here.
I am also running into this same error, but I'm seeing this with the example language server example repo that's in the documentation: https://github.com/Microsoft/vscode-languageserver-node-example