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.

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

Extension development window is not torn down when debugging stops #124128

Closed
connor4312 opened this issue May 18, 2021 · 8 comments
Closed

Extension development window is not torn down when debugging stops #124128

connor4312 opened this issue May 18, 2021 · 8 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues *duplicate Issue identified as a duplicate of another issue(s) extensions-development Issues for developing extensions regression Something that used to work is now broken
Milestone

Comments

@connor4312
Copy link
Member

  1. Debug an extension
  2. Hit stop
  3. The extension host window is still alive

I'm pretty sure this is new today, I was doing js-debug work yesterday and didn't notice it (but might have been behind an Insiders)

@connor4312 connor4312 added the regression Something that used to work is now broken label May 18, 2021
@connor4312
Copy link
Member Author

Interestingly, it seems to work on a hello world extension, but not in js-debug (config). In the logs I see the DAP sessions being torn down gracefully.

@bpasero bpasero removed their assignment May 19, 2021
@bpasero bpasero added the extensions-development Issues for developing extensions label May 19, 2021
@alefragnani
Copy link

I'm facing the same issue on current Insiders and Stable, while debugging any my VS Code extensions.

@isidorn
Copy link
Contributor

isidorn commented Jun 28, 2021

Sorry for the slow response here, looks like a duplicate of #126211
Closing and if you can repro with latest insiders let me know and I can reopen

@isidorn isidorn closed this as completed Jun 28, 2021
@isidorn isidorn added the *duplicate Issue identified as a duplicate of another issue(s) label Jun 28, 2021
@alefragnani
Copy link

It is still happening on Insiders, at least on my scenario (debugging VS Code extensions)

Version: 1.58.0-insider
Commit: bfac07cd0e374c433c2c06d6999dabf9cf9d5d29
Date: 2021-06-28T05:14:49.021Z
Electron: 12.0.12
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: 8.9.255.25-electron.0
OS: Darwin x64 20.5.0

@isidorn
Copy link
Contributor

isidorn commented Jun 29, 2021

Ok let me reopen and I can investigate more

@isidorn isidorn reopened this Jun 29, 2021
@isidorn isidorn added this to the June 2021 milestone Jun 29, 2021
@isidorn
Copy link
Contributor

isidorn commented Jun 30, 2021

I tried to reproduce and I could not. Here are my steps.

  1. Open js-debug repo, choose Extension launch config
  2. Press F5 > new window opens
  3. click on the toolbar Stop action -> second window closes as expected

I tried this 10+ times and every time it worked.
Are you doing something different.
Please note that I have pushed a potential fix for this today, so please try out of source or with Insiders tomorrow.

@isidorn isidorn added info-needed Issue requires more information from poster and removed *duplicate Issue identified as a duplicate of another issue(s) labels Jun 30, 2021
@isidorn isidorn removed this from the June 2021 milestone Jun 30, 2021
@alefragnani
Copy link

I've tested with some of my own extensions, which seems to be simpler than js-debug, so I'm not pretty sure what should be the cause. I've tested with two extensions from vscode-extension-samples with no problem.

The only thing I can easily see as differences between my own extensions and those from vscode-extension-samples and js-debug extensions is the fact that my extension uses Webpack.

I'll test it again tomorrow, and let you know the results.

Thank you

@isidorn isidorn added bug Issue identified by VS Code Team member as probable bug and removed info-needed Issue requires more information from poster labels Jul 29, 2021
@isidorn isidorn added this to the August 2021 milestone Jul 29, 2021
@weinand weinand added the debug Debug viewlet, configurations, breakpoints, adapter issues label Aug 4, 2021
@isidorn
Copy link
Contributor

isidorn commented Aug 12, 2021

Closing as dup of #126911
Since the discussion started there

@isidorn isidorn closed this as completed Aug 12, 2021
@weinand weinand added the *duplicate Issue identified as a duplicate of another issue(s) label Aug 23, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Sep 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues *duplicate Issue identified as a duplicate of another issue(s) extensions-development Issues for developing extensions regression Something that used to work is now broken
Projects
None yet
Development

No branches or pull requests

5 participants