search

microsoft / vscode

Visual Studio Code
https://code.visualstudio.com
MIT License
162.16k stars 28.54k forks source link

VScode crashes on startup with error code 135 #209921

Open FredericBlum opened 5 months ago

FredericBlum commented 5 months ago

Does this issue occur when all extensions are disabled?: No

Steps to Reproduce:

  1. Open VSCode
  2. crash

Similar to other reports (#202962 #202548 ), my VSCode crashes on start-up with error code 135 (and sometimes 132). I have tried the following fixes, which had been reported in the other issues:

The following part of the '--verbose` log might be relevant:

fredericblum@fedora:~$ code --verbose
[0409/091436.200270:ERROR:directory_reader_posix.cc(42)] opendir /home/fredericblum/.config/Code/Crashpad/attachments/75b1bd2b-212e-41f4-90c7-6aa097a2402c: No such file or directory (2)
[18032:0409/091436.267543:WARNING:bluez_dbus_manager.cc(247)] Floss manager not present, cannot set Floss enable/disable.
[main 2024-04-09T07:14:36.386Z] [File Watcher (node.js)] Request to start watching: /home/fredericblum/.config/Code/User (excludes: <none>, includes: <all>, correlationId: <none>),/home/fredericblum/.config/Code/User/settings.json (excludes: <none>, includes: <all>, correlationId: <none>)
[18072:0409/091436.393202:WARNING:sandbox_linux.cc(393)] InitializeSandbox() called with multiple threads in process gpu-process.
[main 2024-04-09T07:14:36.401Z] Starting VS Code
[...]
[main 2024-04-09T07:14:36.455Z] window#load: attempt to load window (id: 1)
[main 2024-04-09T07:14:36.462Z] windowsManager#open used window count 1 (workspacesToOpen: 0, foldersToOpen: 0, emptyToRestore: 0, emptyToOpen: 1)
[main 2024-04-09T07:14:36.462Z] lifecycle (main): phase changed (value: 3)
[main 2024-04-09T07:14:36.463Z] resolveShellEnv(): skipped (VSCODE_CLI is set)
[main 2024-04-09T07:14:36.463Z] update#setState idle
[main 2024-04-09T07:14:36.510Z] resolveShellEnv(): skipped (VSCODE_CLI is set)
[18032:0409/091436.744562:INFO:CONSOLE(655)] "%cTRACE color: #888 workbench#open(): with configuration {"_":[],"diff"
[...]
[18032:0409/091436.744773:INFO:CONSOLE(655)] "%cTRACE color: #888 Renderer->SharedProcess#connect", source: vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js (655)
[18032:0409/091436.750670:INFO:CONSOLE(655)] "%cTRACE color: #888 Renderer->UtilityProcess#createWorker", source: vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js (655)
[main 2024-04-09T07:14:36.757Z] StorageMainService: creating workspace storage (1712646876502)
[18032:0409/091436.782096:INFO:CONSOLE(655)] "%cTRACE color: #888 [lifecycle] starting up (startup kind: 1)", source: vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js (655)
[18032:0409/091436.782461:INFO:CONSOLE(655)] "%cTRACE color: #888 lifecycle: phase changed (value: 2)", source: vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js (655)
[18032:0409/091436.841539:INFO:CONSOLE(655)] "%cTRACE color: #888 TimelineService#registerTimelineProvider: id=timeline.localHistory", source: vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js (655)
Renderer process crashed - see https://www.electronjs.org/docs/tutorial/application-debugging for potential debugging information.
[main 2024-04-09T07:14:37.717Z] CodeWindow: renderer process gone (reason: crashed, code: 135)
[18072:0409/091437.780052:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!
[main 2024-04-09T07:14:38.966Z] lifecycle (main): phase changed (value: 4)
VSCodeTriageBot commented 5 months ago

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.88.0. Please try upgrading to the latest version and checking whether this issue remains.

Happy Coding!

FredericBlum commented 5 months ago

Dear Bot, I have also used the latest stable release, I have only named it last :>

deepak1556 commented 4 months ago

To confirm, do you see the same behavior as https://github.com/microsoft/vscode/issues/202548#issuecomment-1892903268 ? Can you also attach the crash logs following the steps at https://github.com/microsoft/vscode/wiki/Native-Crash-Issues#creating-a-crash-report

FredericBlum commented 4 months ago

No, the behaviour is different. The command written in the linked comment does not fix the issue:

sudo code --no-sandbox --user-data-dir ~/code_root

Running the crash report does not lead to the creation of a .dmp file:

fredericblum@fedora:~$ code --crash-reporter-directory test/
fredericblum@fedora:~$ ls test
fredericblum@fedora:~$
deepak1556 commented 4 months ago

Can you provide an absolute directory path, code --crash-reporter-directory /tmp/test/

FredericBlum commented 4 months ago

Here comes the crash report.

7c64d3c2-9af2-4015-b45e-f62296d6fe91.zip

arianmaghsoudnia commented 2 months ago

I have the same problem. Here are some logs that might help?

[9704:0703/085843.406142:WARNING:bluez_dbus_manager.cc(248)] Floss manager not present, cannot set Floss enable/disable.
[9742:0703/085843.554623:WARNING:sandbox_linux.cc(418)] InitializeSandbox() called with multiple threads in process gpu-process.

[9704:0703/085844.466590:INFO:CONSOLE(655)] "%cTRACE color: #888 Error while resolving configuration file 'file:///path/to/project/.vscode/tasks.json': Unable to read file '/path/to/project/.vscode/tasks.json' (Error: Unable to resolve nonexistent file '/path/to/project/.vscode/tasks.json')", source: vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js (655)
[9704:0703/085844.467318:INFO:CONSOLE(655)] "%cTRACE color: #888 [lifecycle] starting up (startup kind: 1)", source: vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js (655)
[9704:0703/085844.468250:INFO:CONSOLE(655)] "%cTRACE color: #888 lifecycle: phase changed (value: 2)", source: vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js (655)
[9704:0703/085844.474803:INFO:CONSOLE(655)] "%cTRACE color: #888 Error while resolving configuration file 'file:///another/path/.vscode/settings.json': Unable to read file '/another/path/.vscode/settings.json' (Error: Unable to resolve nonexistent file '/another/path/.vscode/settings.json')", source: vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js (655)
[9704:0703/085844.475391:INFO:CONSOLE(655)] "%cTRACE color: #888 Error while resolving configuration file 'file:///another/path/.vscode/tasks.json': Unable to read file '/another/path/.vscode/tasks.json' (Error: Unable to resolve nonexistent file '/another/path/.vscode/tasks.json')", source: vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js (655)
[9704:0703/085844.476021:INFO:CONSOLE(655)] "%cTRACE color: #888 Error while resolving configuration file 'file:///another/path/.vscode/launch.json': Unable to read file '/another/path/.vscode/launch.json' (Error: Unable to resolve nonexistent file '/another/path/.vscode/launch.json')", source: vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js (655)

[0703/085845.096987:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0703/085845.098313:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0703/085845.137551:ERROR:directory_reader_posix.cc(43)] opendir /home/user/.config/Code/Crashpad/attachments/unique-identifier: No such file or directory (2)