Closed paulfouquet closed 10 months ago
It is now crashing every time I launch it. I've re-install it twice using the following process and did not use any Devcontainer this time.
sudo apt-get remove code
rm -r ~/.config/Code/
sudo apt install ./code_1.74.2-1671533413_amd64.deb
I am not sure if it is related to using a devcontainer anymore, but the issue started since I did use a devcontainer.
Please let me know if any update or need more information to investigate.
Symbolicated log: symbolicated-output.log
The crash occurs in views::DesktopNativeWidgetAura::OnWindowActivated
in desktop_native_widget_aura.cc
. I noticed Chromium commit bf79dad adds in a null check for native_widget_delegate_
, so I speculate that that is where the crash is occurring.
For reference, the commit above was first released in Chromium M109, which is available in Electron 23. VS Code 1.74.2 uses Electron 19.1.8.
Does the crash repro when you run with --ozone-platform="wayland" --enable-features="WaylandWindowDecorations"
?
I am not able to launch VSCode with this command:
❯ code --ozone-platform="wayland" --enable-features="WaylandWindowDecorations" --verbose
Warning: 'ozone-platform' is not in the list of known options, but still passed to Electron/Chromium.
Warning: 'enable-features' is not in the list of known options, but still passed to Electron/Chromium.
[0201/150145.864830:ERROR:file_io_posix.cc(152)] open /home/paul/.config/Code/Crashpad/pending/1fff74d6-6a4e-4ac6-9a18-b4c149c353a2.lock: File exists (17)
[0201/150145.864871:ERROR:file_io_posix.cc(152)] open /home/paul/.config/Code/Crashpad/pending/5968ec67-71a1-4a8f-8adc-5ea0dedbd521.lock: File exists (17)
[152764:0201/150145.865528:ERROR:wayland_connection.cc(209)] Failed to connect to Wayland display
[152764:0201/150145.865576:ERROR:ozone_platform_wayland.cc(226)] Failed to initialize Wayland platform
[152764:0201/150145.865579:ERROR:env.cc(226)] The platform failed to initialize. Exiting.
The futex facility returned an unexpected error code.
[0201/150145.866997:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0201/150145.895788:ERROR:directory_reader_posix.cc(42)] opendir /home/paul/.config/Code/Crashpad/attachments/658bf380-c8e3-493a-8138-7c6823f55d08: No such file or directory (2)
Seems like you are running under Xorg, you would need to switch your desktop enviroment to use wayland and then try.
I enabled wayland
and tried again, still not able to open VSCode:
If I uninstall VSCode sudo apt-get purge code
and remove the associated files in ~/.vscode
and ~/.config/Code
and re-install VSCode again, I am able to launch VSCode the first time. If I exit it (without doing anything with it prior) and try to launch it again, it fails.
@deepak1556 As per #180283 I tried what you suggested by launching
code-insiders --verbose --log debug --disable-extensions --user-data-dir /tmp/vscode-focus
But still the issue occurs.
@0xteo does the issue repro with latest stable v1.78
?
@deepak1556 Yes, still occurs with 1.78.2
stable. First time around it does work though, from the second time it stops working.
The last working version for me is 1.73.1-1667967334
on stable.
Thanks for testing, can you provide the crash logs for 1.78
since we have updated the runtime version in this release.
Please check if the issue is present with latest stable 1.85
, attach new crash logs if it does.
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!
I have this issue with one of my devcontainers also. I started happening on my Windows 11 with WSL2, first time i launch it and open in devcontainer it works and then next time i open VSCode it freezes during the process of installing extensions. VSCode freezes and I need to close it by the popup. If I open it again and not using the devcontainer it works.
I bought an Macbook M3 Pro instead and cloned my repo, opened VSCode, re-opened in Devcontainer and it worked flawless first time. Exit VSCode, container closes, open VSCode again, re-opened in Devcontainer -- VSCode freezes during extension initialization.
Im able to use VSCode and the docker containers without any issues as long as i dont use the devcontainer option.
Ive tried VSCode troubleshooting to disable/enable each extension -- didnt help. No issues found. Ive tried to clean all container images/volumes in docker, restart with clear cache option -- same issue, freezes during Devcontainer.
Im new to Apple, how can I provide logs for you?
Version: 1.86.0
Commit: 05047486b6df5eb8d44b2ecd70ea3bdf775fd937
Date: 2024-01-31T10:29:11.933Z (5 days ago)
Electron: 27.2.3
ElectronBuildId: 26495564
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: 11.8.172.18-electron.0
OS: Darwin arm64 23.3.0
@beejaz I recommend creating a new issue with a crash report if possible. The Native Crash Issues page on the wiki explains how to create a crash report.
Does this issue occur when all extensions are disabled?: Yes
Steps to Reproduce: I am not able to find a way to reproduce all the time yet, as the only solution I've found yet to get VSCode working again is to uninstall, clear the cache and install it again...
Most of the time that is how it happens:
Traces (I closed the window after waiting half a minute)
``` ❯ code --verbose [1550774:0111/080207.859793:WARNING:bluez_dbus_manager.cc(248)] Floss manager not present, cannot set Floss enable/disable. [1550812:0111/080208.018085:WARNING:sandbox_linux.cc(376)] InitializeSandbox() called with multiple threads in process gpu-process. [main 2023-01-10T19:02:08.023Z] [File Watcher (node.js)] Request to start watching: /home/paul/.config/Code/User (excludes:I've followed the process: https://github.com/microsoft/vscode/wiki/Native-Crash-Issues#creating-a-crash-report A
.dmp
file has been saved in thepending
folder only: 915824c2-b41e-495f-a623-221878bda069.zipDevcontainer configuration
## `Dockerfile` ``` FROM osgeo/gdal:ubuntu-small-3.6.1 RUN apt update && apt install -y python3-pi p python3-distutils git RUN curl -sSL https://install.python-poetry.org | python3 - # Allowing access to osgeo/gdal python library within the venv environment created with Poetry ENV PYTHONPATH="/lib/python3/dist-packages:/workspaces/topo-imagery:$PYTHONPATH" ENV PATH=/root/.local/bin:$PATH ``` ## `devcontainer.json` ``` // For format details, see https://aka.ms/devcontainer.json. For config options, see the // README at: https://github.com/devcontainers/templates/tree/main/src/docker-existing-dockerfile { "name": "topo-imagery-dev", "context": "..", "dockerFile": "Dockerfile", "customizations": { "vscode": { "settings": { "terminal.integrated.profiles.linux": { "bash": { "path": "/bin/bash" } }, "editor.codeActionsOnSave": { "source.organizeImports": true }, "python.defaultInterpreterPath": "${containerWorkspaceFolder}/.venv/bin/python3.10", "python.formatting.blackPath": "${containerWorkspaceFolder}/.venv/bin/black", "python.linting.mypyPath": "${containerWorkspaceFolder}/.venv/bin/mypy", "python.linting.pylintPath": "${containerWorkspaceFolder}/.venv/bin/pylint", "python.formatting.provider": "black", "python.testing.pytestEnabled": true, "python.linting.enabled": true, "python.linting.pylintEnabled": true, "editor.formatOnSave": true, "autoDocstring.docstringFormat": "google-notypes" }, "extensions": [ "ms-python.python", "ms-python.vscode-pylance", "esbenp.prettier-vscode", "njpwerner.autodocstring" ] } }, "postCreateCommand": "bash ./.devcontainer/post_create.sh", "postStartCommand": "bash ./.devcontainer/post_start.sh ${containerWorkspaceFolder}", "mounts": [ "source=${localEnv:HOME}${localEnv:USERPROFILE}/.aws,target=/root/.aws,type=bind", "source=${localEnv:HOME}${localEnv:USERPROFILE}/.bashrc,target=/root/.bashrc,type=bind,consistency=cached" //"source=${localEnv:HOME}${localEnv:USERPROFILE}/tmp,target=/tmp,type=bind" ], // https://containers.dev/features // NOTE: installing Git in that way took more time than within the Dockerfile "features": { "ghcr.io/devcontainers/features/docker-in-docker:2": {} }, "waitFor": "postCreateCommand" } ``` ## `post_create.sh` ``` #!/bin/bash poetry config cache-dir $(pwd)/.cache poetry config virtualenvs.in-project true ``` ## `post_started.sh` ``` #!/bin/bash set -e # Install all dependencies with poetry poetry install --no-interaction git config --global --add safe.directory $1 poetry run pre-commit install ```