-
Notifications
You must be signed in to change notification settings - Fork 357
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Debugger listening but program not starting #362
Comments
Hey there, thx for reporting this. We just added a live diagnostics feature to help us get to the bottom of issues like this that are difficult for us to repro - mind trying it out? More details here: #246 (comment) |
The Live Diagnostics output from run where it's working, and one run where it isn't would be helpful so we have a basis of comparison. |
Thanks, i have installed the NTVS.Dev.2015-08-04 versions and have enabled diagnostics. If i run into this problem again with this version of nodejs tools, I will get back to you with diagnostic information to help you pin down the bug. |
Here is a log from when it fails.
|
Tried to paste an example of success but the post became too long and was not accepted. If you need one, let me know how to send it to you. |
Thanks. I notice at the top you mention having a breakpoint or an exception on the first line. Is it only at the start of the initial script you have this problem? Asking as I noticed this code in NodeJS when browsing the other day: https://github.com/joyent/node/blob/master/src/node.js#L116 . If you read the comment there, it may well be a known NodeJS issue. The other interesting output above it the number of times its calling setExceptionBreak with apparently the same args. I doubt this is the cause, but doesn't look right. Have you changed exception settings at all? |
With having a breakpoint on the first line i meant that it was something i set temporarly for testing purpose to see if it reached any of my code, it is not something i normally have, and it does not mather |
doesn't matter where i have the breakpoint. Not sure what you mean by start of initial script. Regarding exceptions i have turned off debuk breaking on a couple of exceptions since it does not seem to be a way to only have breaking on uncaught exceptions. Brw is there a way to edit posts? Cant see an option when browsing with iphone at least. Was going to edit a word and accidentally clicked post instead. |
Hey guys - We are experiencing this too even with the hello world project template. It happens A LOT in fact 95% of the time. Running windows 7, Visual Studio 2013 update 4 Running node tools version 1. |
David, i had the same problem until i downloaded the latest dev build at https://github.com/Microsoft/nodejstools/releases now i have only experienced it once this week instead of every other run. Also see this post for info on how to get a debug log you can provide them to help them track down the issue, as they can not reproduce it themself: #246 (comment) |
Unfortunately working for a bank they will not allow me to download software from the internet. :-( Any other ideas? |
@Davidhanson90 add |
Not seen any updates on this for a while, is there anything else i can do to make it easier for you guys to solve this problem? |
@noopole adding debugger to first line causes visual studio to crash and restart, in the console window i get the following text when it does. |
@endasil the error in the console looks like the issue I've opened at #425 . For that I have a repro, however this isn't crashing VS at all, just messing up the Node process (which seems like a Node bug actually - as all that's happening is the debugger is sending a 'disconnect' on the socket, which shouldn't cause Node to crash). Are you getting any events in the Event Log for the VS crash that would help us see the call stack where this is happening? |
I've posted another log of this issue in #433 |
The issue based on the logs appears to stem from sending an AD7LoadCompleteRunningEvent when we should be sending an AD7LoadCompleteEvent because for some reason processLoadedRunning is set to true here even though execution is paused.
Investigating this further... |
Braindumping some more notes as I look into this... Also interesting is that there are two backtrace requests - the first returns "running":"true" (which is presumably why we think the app is actually running rather than paused) and the second returns much later with "running":"false" |
VS2015, 1.1RC2 I have debugger not attached, and restart debugger. Issue reappear again:
I would also suggest add more information about debugger event parameters. For example modules loaded, or function execution results. |
Same issue with 1.1RC2.1
And now from the good session.
The only difference which I see is that Debuggerconnection event |
Thank you! I will try it out and see if helps with my debugging issues! |
The issue reappear for me in the latest Dev release (9-17-2015 Dev Build). The output from the Live Diagnostics window
|
@mousetraps @billti Please take a look. |
@kant2002 can you verify thats the full output for that session? |
Yes @mousetraps. That's was the full output for whole session. I specifically wait couple minutes to double check. Nothing more happens. |
Please reopen issue, since it not fully fixed. Do you need me to reproduce issue again? I'm sure that race condition still exists. |
I have run into this problem again a couple of times the last week. Several days can pass between me having this problem so it seems to be a less frequent problem than the previous. Here is a log, let me know if there is anything else i can provide you with to help you track down the error.
|
I am unable to run Node.js and Express 4 apps in Visual Studio 2015 Community Edition. The debugger listens on port 5858. Then a dialog pops up with the caption 'Operation taking longer than expected.'
|
Thanks @jasonalls . I've not seen that dialog be an issue in NTVS before. Searching on that specific dialog generally shows issues with 3rd party components or firewall configuration. I can see if your DLL list above quite a number of 3rd party extensions. Are you seeing this reproduce consistently with any project? Has this started recently or always been an issue (and if recently, have you installed/configured any other software/extensions around the time this started occurring)? |
Hi Bill, It has always been an issue, and is consistent across all project types. Hope this helps. I will have another look tomorrow, and see if I can find a solution. If I do, I will let you know. Kind Regards, Jason. Date: Mon, 16 Nov 2015 09:39:38 -0800 Thanks @jasonalls . I've not seen that dialog be an issue in NTVS before. Searching on that specific dialog generally shows issues with 3rd party components or firewall configuration. I can see if your DLL list above quite a number of 3rd party extensions. Are you seeing this reproduce consistently with any project? Has this started recently or always been an issue (and if recently, have you installed/configured any other software/extensions around the time this started occurring)? — |
Any update for it? I am having the exact issue |
@KseniaIV Can you please share:
Also, before launching, go to |
Closing as no repo. If you are seeing this, please open a new issue so that we can investigate further. Thanks. |
Sometimes when i choose to debug a project (debug -> Start Debugging or pressing F5), i will se "Debugger listening on port 5858" in the console window, but the program will not actually run. If i add a breakpoint to first line in the code, throw an exception on the first line or whatever, it will never get so far, no code is executed. If i stop and start the program multiple times it will eventually run, but this is a rather annoying process. I have nodejs v0.12.7. Tried visual studio 2013 and visual studio 2015. Upgraded from windows 8.1 to 10 and it is the same on both platforms.
The text was updated successfully, but these errors were encountered: