Skip to content

"Start without debug" only works a single time, then hangs #341

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

Closed
mvtk opened this issue Dec 4, 2017 · 2 comments
Closed

"Start without debug" only works a single time, then hangs #341

mvtk opened this issue Dec 4, 2017 · 2 comments
Labels
area-debugging bug Issue identified by VS Code Team member as probable bug

Comments

@mvtk
Copy link

mvtk commented Dec 4, 2017

Environment data

VS Code version: 1.18.1
Python Extension version: 0.8.0
Python Version: 2.7.14 AMD64
OS and version: Windows 7 x64

Actual behavior

When running python scripts (both via "Start without debugging" or "Start with debugging") the currently open script is executed as expected but python never returns. I can see the python running indicator in the status bar and i can not restart the script. I can also not use the stop shortcut or menu entry. The only way to start the script again is to relaunch vscode. Note that the actual python process IS shutting down. If i select a debug config and hit start it actually jumps in. But if i hit stop in the debug toolbar the python entry in the stack view stays "running" and the blue progress indicator line on top of the debug bar keeps running forever.

Also note that i did try various changes to launch.json. Including reducing it to a single config:

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Python",
            "type": "python",
            "request": "launch",
            "stopOnEntry": true,
            "pythonPath": "C:\\Users\\tkaufmann\\Envs\\seiko\\Scripts\\python.exe",
            "program": "${file}",
            "cwd": "${workspaceRoot}",
            "env": {},
            "envFile": "${workspaceRoot}/.env",
            "debugOptions": [
                //"WaitOnAbnormalExit",
                //"WaitOnNormalExit",
                "RedirectOutput"
            ]
        },
    ]
}

Expected behavior

Running a script via "Start without debugging" should just return to normal state afterwards.

Steps to reproduce:

  • Simply run a script using the shortcut or the menu entry

Logs

Output from Python output panel

----------Generating Tags----------
ctags --options=C:\Users\tkaufmann\.vscode\extensions\ms-python.python-0.8.0\resources\ctagOptions --languages=Python --exclude=**/site-packages/** -o d:\dev\.vscode\tags .
##########Linting Output - pylint##########

**snip skipping linting output**

Output from Console window (Help->Developer Tools menu)

console.ts:123 [Extension Host] rejected promise not handled within 1 second
t.log @ console.ts:123
shell.ts:459 spawn ctags ENOENT: Error: spawn ctags ENOENT
	at exports._errnoException (util.js:1050:11)
	at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
	at onErrorNT (internal/child_process.js:367:16)
	at _combinedTickCallback (internal/process/next_tick.js:80:11)
	at process._tickCallback (internal/process/next_tick.js:104:9)
e.onUnexpectedError @ shell.ts:459
console.ts:123 [Extension Host] (node:5704) DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
t.log @ console.ts:123

@mvtk
Copy link
Author

mvtk commented Dec 4, 2017

Note: Disabling ctags makes the ctags error in the console go away, the behavior stays the same. Also note, that there was hinted this may be caused by running 32bit python with 64bit code, but this is not the case for me. Both 64bit.

@DonJayamanne
Copy link

Duplicate of #242

@DonJayamanne DonJayamanne marked this as a duplicate of #242 Dec 4, 2017
@DonJayamanne DonJayamanne added closed-duplicate area-debugging bug Issue identified by VS Code Team member as probable bug labels Dec 4, 2017
@lock lock bot locked as resolved and limited conversation to collaborators Jul 12, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-debugging bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

No branches or pull requests

2 participants