VScode doesn't close on Cmd-Q

[andig]

Issue Type: Bug

Sometimes closing VScode with Cmd-Q is (apprently) ignored. It continues to work (writing this issue in a "closed" instanced) and can still be force-killed using process manager. This seems to happen sind last release.

VS Code version: Code 1.68.1 (Universal) (30d9c6cd9483b2cc586687151bcbcd635f373630, 2022-06-14T12:52:13.188Z) OS version: Darwin arm64 21.5.0 Restricted Mode: No

System Info

|Item|Value| |---|---| |CPUs|Apple M1 (8 x 24)| |GPU Status|2d_canvas: enabled
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
metal: disabled_off
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_renderer: enabled_on
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled| |Load (avg)|5, 3, 2| |Memory (System)|16.00GB (0.09GB free)| |Process Argv|--crash-reporter-id 171ce63a-8329-4c58-b846-cfd00e6e8d88| |Screen Reader|no| |VM|0%|

Extensions (63)

Extension|Author (truncated)|Version ---|---|--- terraform|4op|0.2.5 vscode-sqlite|ale|0.14.1 vscode-color|ans|0.4.5 unique-lines|bib|1.0.0 markdown-checkbox|bie|0.3.2 markdown-footnotes|bie|0.0.7 markdown-mermaid|bie|1.14.2 vscode-intelephense-client|bme|1.8.2 better-toml|bun|0.3.2 gotemplate|cas|0.4.0 dart-code|Dar|3.42.1 vscode-markdownlint|Dav|0.47.0 vscode-eslint|dba|2.2.2 docs-yaml|doc|0.2.8 githistory|don|0.6.19 xml|Dot|2.5.1 vscode-html-css|ecm|1.13.0 EditorConfig|Edi|0.16.4 json-tools|eri|1.0.2 prettier-vscode|esb|9.5.0 fold-unfold-all-icone|Fer|0.0.3 copilot|Git|1.30.6165 remotehub|Git|0.34.0 go|gol|0.34.0 vscode-graphql|Gra|0.4.13 todo-tree|Gru|0.0.215 terraform|has|2.23.0 beautify|Hoo|1.5.0 composer|ika|0.8.0 flux|inf|1.0.4 search-editor-apply-changes|jak|0.1.1 vscode-graphviz|joa|0.0.6 graphql-for-vscode|kum|1.15.3 vscode-docker|ms-|1.22.0 python|ms-|2022.8.0 vscode-pylance|ms-|2022.6.30 jupyter|ms-|2022.5.1001601848 jupyter-keymap|ms-|1.0.0 jupyter-renderers|ms-|1.0.8 hexeditor|ms-|1.9.7 remote-repositories|ms-|0.12.0 sublime-keybindings|ms-|4.0.10 vscode-github-issue-notebooks|ms-|0.0.119 vsliveshare|ms-|1.0.5625 vsliveshare-audio|ms-|0.1.91 vsliveshare-pack|ms-|0.4.0 php-docblocker|nei|2.7.0 indent-rainbow|ode|8.3.1 proto|pet|0.0.2 vscode-commons|red|0.0.6 vscode-xml|red|0.20.0 vscode-yaml|red|1.8.0 semgrep|Sem|0.3.1 bash-beautify|sha|0.1.1 mdx|sil|0.1.0 prettier-vscode|Sim|2.0.7 code-spell-checker|str|2.2.5 pdf|tom|1.2.0 volar|Vue|0.38.1 change-case|wma|1.0.0 php-debug|xde|1.27.0 markdown-all-in-one|yzh|3.4.3 vscode-proto3|zxh|0.5.5

A/B Experiments

``` vsliv368:30146709 vsreu685:30147344 python383cf:30185419 vspor879:30202332 vspor708:30202333 vspor363:30204092 vslsvsres303:30308271 pythonvspyl392:30443607 vserr242:30382549 pythontb:30283811 vsjup518:30340749 pythonvspyt551:30345470 pythonptprofiler:30281270 vsdfh931cf:30280410 vshan820:30294714 vstes263cf:30335440 pythondataviewer:30285071 vscod805cf:30301675 binariesv615:30325510 bridge0708:30335490 bridge0723:30353136 vsaa593:30376534 vsc1dst:30438360 pythonvs932:30410667 wslgetstarted:30449410 vscscmwlcmt:30465135 cppdebug:30492333 pylanb8912:30515786 vsclangdf:30486550 c4g48928:30515882 ```

[deepak1556]

Can you launch with code --verbose and attach the output when the quit does not work as expected. Also does the issue repro with latest insiders https://code.visualstudio.com/insiders ?

[andig]

Unfortunately it happens only sometimes. Can I configure the --verbose to be applied on each start (e.g. when invoking via Cmd-Space)? Where can I pick up the output?

[PabloLION]

Weird. I'm with M1 and it never happened to me.

[andig]

Can I configure the --verbose to be applied on each start (e.g. when invoking via Cmd-Space)? Where can I pick up the output?

Any help with this question? It's still happening but never when I started it intentionally with --verbose...

[andig]

Had this issue once more today and saw this in the startup shell, apparently connected to using git from inside VScode:

You have not agreed to the Xcode license agreements, please run 'sudo xcodebuild -license' from within a Terminal window to review and agree to the Xcode license agreements.

Not sure it's related though...

[vscodenpa]

Hey @deepak1556, this issue might need further attention.

@andig, you can help us out by closing this issue if the problem no longer exists, or adding more information.

[andig]

Problem still exists. To provide more info I'd still need to understand how to do this:

Where can I pick up the output?

https://github.com/microsoft/vscode/issues/153098#issuecomment-1243461701

[vscodenpa]

Hey @deepak1556, this issue might need further attention.

@andig, you can help us out by closing this issue if the problem no longer exists, or adding more information.

[andig]

It is still a problem, I do meanwhile see it with other programs on Mac too, though. Might be more a MacOS than a VScode issue.

[vscodenpa]

Hey @deepak1556, this issue might need further attention.

@andig, you can help us out by closing this issue if the problem no longer exists, or adding more information.