<h1 dir="auto">Environment</h1>
<p dir="auto">Windows build number: 10.0.18362.239<br>
Windows Terminal version (if applicable): 0.3<br>
Relatively clean OS, Ubuntu and WSL installed.</p>
<h1 dir="auto">Steps to reproduce</h1>
<ol dir="auto">
<li>Open the Terminal app</li>
<li>Close the Terminal app</li>
</ol>
<p dir="auto">Only happens when the terminal is closed and PS is the active tab. Does not happen if Ubuntu or command line is the active tab or if I close a PS tab but Terminal app stays open.</p>
<h1 dir="auto">Expected behavior</h1>
<p dir="auto">I expect it to close with no errors</p>
<h1 dir="auto">Actual behavior</h1>
<p dir="auto">An error pops out telling me that "PowerShell has stopped working" as in the screenshot.<br>
"Standard" PowerShell works just fine.</p>
<p dir="auto"><a target="_blank" rel="noopener noreferrer nofollow" href="https://user-images.githubusercontent.com/29314003/62493451-0f07f500-b7c9-11e9-83de-13369874dac3.png"><img width="265" alt="PowerShell has stopped working error in Terminal" src="https://user-images.githubusercontent.com/29314003/62493451-0f07f500-b7c9-11e9-83de-13369874dac3.png" style="max-width: 100%;"></a></p>
<p dir="auto">We have a job object for the conhost in PTY mode that is supporting the connection on each tab. But this was because the conhosts weren't exiting.</p>
<p dir="auto">However, conhosts should just exit when they have nothing to do.</p>
<p dir="auto">This represents taking the job object off and figuring out what the actual underlying issue is that is keeping the conhost from realizing it can just exit.</p>