Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Debugger creates processes every second #5267

Closed
crazyyzarc opened this issue Apr 7, 2020 · 3 comments
Closed

Debugger creates processes every second #5267

crazyyzarc opened this issue Apr 7, 2020 · 3 comments
Labels
Issue-Question For questions or discussion Needs-Attention The core contributors need to come back around and look at this ASAP. Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Product-Terminal The new Windows Terminal. Resolution-Answered Related to questions that have been answered

Comments

@crazyyzarc
Copy link

crazyyzarc commented Apr 7, 2020 •
edited

Environment

Windows build number: W10 RB1903 18362.752
Windows Terminal version (if applicable): 0.10.781.0

Any other software?

Steps to reproduce

1. open regedit.exe
2. add new key cmd.exe in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\
3. add new Debugger string with value to windows terminal "C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.10.781.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe"
4. run cmd.exe
5. enjoy how windows terminal is opened thousands of times ;)

https://framapic.org/FXcZwQgGbBPZ/bYYEfDIIPOXj.png

Expected behavior

open once only

Actual behavior

see step 5.
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Apr 7, 2020
@zadjii-msft
Copy link
Member

y tho

Is this really a bug, or expected behavior? I bet your default profile for the Terminal is a cmd.exe profile. Whenever you launch cmd.exe, Windows is going to open a new WT instance, which is going to start cmd.exe as your default profile, which is going to cause Windows to open a new WT instance, ...

This is very much by-design. Do you have some other design or use case in mind?

@zadjii-msft zadjii-msft added Issue-Question For questions or discussion Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Product-Terminal The new Windows Terminal. Resolution-Answered Related to questions that have been answered labels Apr 7, 2020
@DHowett-MSFT
Copy link
Contributor

I think what they want is #492

@crazyyzarc
Copy link
Author

I think what they want is #492

Yes, when I use the command cmd.exe, I want to open a WT instance instead of system32\cmd.exe

@ghost ghost added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels Apr 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Question For questions or discussion Needs-Attention The core contributors need to come back around and look at this ASAP. Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Product-Terminal The new Windows Terminal. Resolution-Answered Related to questions that have been answered
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@crazyyzarc @DHowett-MSFT @zadjii-msft