-
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 calls AD7Engine Finalized too soon #823
Comments
I don't know if it could help but I notice that If I stop the debugger using Visual Studio menu [Debug + Stop Debugging] the problem occurred more frequently than stopping the program by closing the console. If I'm only closing the console each time the problem occur rarely. |
@purell To unblock yourself, try using VS 2015 Update 2 and NTVS 1.2 Alpha. I've tried to repo the issue using the latest versions and Node v0.12.0, but was not able to. Either way, I think we should add more diagnostic logging to the AD7Engine so we can better investigate this sort of problem. |
Closing. @purell please give our most recent releases a try and let me know if you are still seeing this issue. Thanks. |
Hi, I've got this same issue and it's always been like this on my PC (since I started using Node Tools quite a long time ago), it seems to be worse with the 1.2 release. My config is below and this is the diagnostics log when the debugger refuses to start.
Setup:
|
Copied from @purell #246 (comment)
@mousetraps : I did what you said about the "Diagnostic Info" windows and this is what I got when the debugger doesn't start :
Normaly before the Finalized line we are suppose to the the debugger trying to connect (Debugger connecting to URI: tcp://localhost:....) but the log stop there and the action too.
By the way, is it helping you more ?
My Configuration :
This problem is more than annoying now, I have to relaunch Visual Studio 2013 a lot of time per hours while developing. I think that in a day I can relaunch it 100 times ! Even if I don't like Webstorm, I think that I will come back to it very shortly :(
Maybe we should re-open the case ?
The text was updated successfully, but these errors were encountered: