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

Leaked debug processes on VS Code reload window #6917

Closed
Tracked by #5607
kieferrm opened this issue Jul 29, 2021 · 2 comments
Closed
Tracked by #5607

Leaked debug processes on VS Code reload window #6917

kieferrm opened this issue Jul 29, 2021 · 2 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug notebook-debugging notebook-run-by-line

Comments

@kieferrm
Copy link
Member

kieferrm commented Jul 29, 2021

Issue Type: Bug

  1. enable experimental debugging
  2. open a notebook
  3. run a cell line-by-line (or use full debugging - doesn't matter)
  4. while debugging is running reload window
    -> debug process is still hanging around

I ran this in a codespace.

When I run the same steps but using the js debugger, no process leaks.

Extension version: 2021.8.1077987658
VS Code version: Code - Insiders 1.59.0-insider (0f22f2d343e33b03e8033d1083513072f58ece21, 2021-07-29T05:27:33.986Z)
OS version: Darwin arm64 20.6.0
Restricted Mode: No
Remote OS version: Linux x64 5.8.0-1039-azure
Remote OS version: Linux x64 5.4.0-1055-azure

System Info
Item Value
CPUs Apple M1 (8 x 24)
GPU Status 2d_canvas: enabled
gpu_compositing: enabled
metal: disabled_off
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
rasterization: enabled
skia_renderer: disabled_off_ok
video_decode: enabled
webgl: enabled
webgl2: enabled
Load (avg) 2, 2, 3
Memory (System) 16.00GB (0.40GB free)
Process Argv --enable-proposed-api lszomoru.lszomoru-proposed-api-sample --enable-proposed-api donjayamanne.kusto --crash-reporter-id ef10dfea-3602-4c74-ba1a-109ce7da7825
Screen Reader no
VM 0%
Item Value
Remote SSH: az-devbox
OS Linux x64 5.8.0-1039-azure
CPUs Intel(R) Xeon(R) Platinum 8171M CPU @ 2.60GHz (4 x 2095)
Memory (System) 15.64GB (12.53GB free)
VM 0%
Item Value
Remote Codespaces
OS Linux x64 5.4.0-1055-azure
CPUs Intel(R) Xeon(R) Platinum 8168 CPU @ 2.70GHz (4 x 2693)
Memory (System) 7.78GB (0.54GB free)
VM 0%
A/B Experiments
vsliv695:30137379
vsins829:30139715
vsliv368:30146709
vsreu685:30147344
python383:30185418
pythonvspyt602:30291494
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyt639:30291487
pythontb:30258533
pythonvspyt551:30291412
vspre833:30321513
pythonptprofiler:30281269
vshan820:30294714
pythondataviewer:30285072
vscus158:30321503
pythonvsuse255:30319630
vscod805cf:30301675
pythonvspyt200:30323110
vsccppwt:30312692
pythonvssor306:30340298
bridge0708:30335490
dockerwalkthrucf:30344902

@kieferrm kieferrm added the bug Issue identified by VS Code Team member as probable bug label Jul 29, 2021
@greazer
Copy link
Contributor

greazer commented Aug 2, 2021

Dupe of issue David mentions above.

@greazer greazer closed this as completed Aug 2, 2021
@DavidKutu DavidKutu reopened this Aug 2, 2021
@greazer greazer reopened this Aug 2, 2021
@greazer greazer added this to the On Deck milestone Oct 8, 2021
@greazer greazer changed the title Leaking debug processes Leaked debug processes on VS Code reload window Oct 8, 2021
@roblourens
Copy link
Member

This is fixed

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 14, 2023
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 notebook-debugging notebook-run-by-line
Projects
None yet
Development

No branches or pull requests

5 participants