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

crash on start after upgrade to macos sequoia #229463

Open
ungoldman opened this issue Sep 24, 2024 · 10 comments
Open

crash on start after upgrade to macos sequoia #229463

ungoldman opened this issue Sep 24, 2024 · 10 comments
Assignees
Labels
info-needed Issue requires more information from poster

Comments

@ungoldman
Copy link

ungoldman commented Sep 24, 2024

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

  • VS Code Version: 1.93.1
  • OS Version: MacOS 15.0 (Sequoia)

Steps to Reproduce:

After upgrade MacOS to 15.0 (Sequoia)...

  1. Start VSCode from Dock
  2. Closes immediately, no crash report

Alternate path to reproduce bug:

  1. Open folder or file from command-line using code shell command
  2. Closes after a short time, or immediately after trying to open any VSCode menu in the system menu bar

Details:

Looked through logs in $HOME/Library/Application Support/Code/logs, only anomaly I found was this in sharedprocess.log:

2024-09-23 17:37:27.439 [error] [uncaught exception in sharedProcess]: Event not found: onDidChange: CodeExpectedError: Event not found: onDidChange
    at Object.listen (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:45:4960)
    at E.t (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:44:251)
    at E.q (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:43:4371)
    at y.value (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:43:3602)
    at d.y (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:38:1902)
    at d.z (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:38:1972)
    at d.fire (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:38:2188)
    at MessagePortMain.fe (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:36:30382)
    at MessagePortMain.emit (node:events:514:28)
    at Object.emit (node:electron/js2c/utility_init:2:2285)

Confirmed this is still happening after opening with --disable-extensions flag.

Don't see anyone else reporting this behavior yet so thought it was worth opening. I'm using latest version of Codium as an alternative and that's been working fine.

Other system details:

  • 2023 14-inch MBP
  • Apple M2 Pro chip
  • 16GB memory

This is a relatively untouched machine, it's a personal laptop with not much on it other than standard software development tools.

@deepak1556
Copy link
Collaborator

Exception in the shared process shouldn't bring down the application, looks like the issue might be something else. Can you provide the output of code --verbose. Also does the issue happen with latest insiders https://code.visualstudio.com/insiders

@deepak1556 deepak1556 added the info-needed Issue requires more information from poster label Sep 24, 2024
@sylvia-liu-qinghua
Copy link

I have also been experiencing similar issues since upgrading to Sequoia yesterday...
running code --verbose return me these:
[main 2024-09-24T08:27:30.195Z] [File Watcher (node.js)] Request to start watching: /Users/xxx/Library/Application Support/Code/User (excludes: <none>, includes: <all>, correlationId: <none>),/Users/xxx/Library/Application Support/Code/User/settings.json (excludes: <none>, includes: <all>, correlationId: <none>) [main 2024-09-24T08:27:30.198Z] Sending env to running instance... [main 2024-09-24T08:27:30.200Z] [File Watcher (node.js)] Started watching: '/Users/xxx/Library/Application Support/Code/User' [main 2024-09-24T08:27:30.200Z] [File Watcher (node.js)] Started watching: '/Users/xxx/Library/Application Support/Code/User/settings.json' [main 2024-09-24T08:27:30.230Z] Sent env to running instance. Terminating... [main 2024-09-24T08:27:30.230Z] Lifecycle#kill() [main 2024-09-24T08:27:30.230Z] Lifecycle#onWillShutdown.fire()

@deepak1556
Copy link
Collaborator

@sylvia-liu-qinghua can you close all running VSCode processes and run the command again. The previous output shows there is an active instance of the application.

@sylvia-liu-qinghua
Copy link

@deepak1556 should I first launch VS code or just write in my terminal code --verbose to launch it?

@deepak1556
Copy link
Collaborator

Run code --verbose from the terminal which will launch the application and emit verbose logs to the terminal

@sylvia-liu-qinghua
Copy link

I got this output (which did not launch VS code)!!
But most of the time it does successfully launch the app normally as well
[main 2024-09-24T08:53:23.602Z] [File Watcher (node.js)] Request to start watching: /Users/xx/Library/Application Support/Code/User (excludes: <none>, includes: <all>, correlationId: <none>),/Users/xxx/Library/Application Support/Code/User/settings.json (excludes: <none>, includes: <all>, correlationId: <none>) [main 2024-09-24T08:53:23.611Z] Starting VS Code [main 2024-09-24T08:53:23.611Z] from: /Applications/Visual Studio Code.app/Contents/Resources/app [main 2024-09-24T08:53:23.611Z] args: { _: [], diff: false, merge: false, add: false, goto: false, 'new-window': false, 'reuse-window': false, wait: false, help: false, 'list-extensions': false, 'show-versions': false, 'pre-release': false, 'update-extensions': false, version: false, verbose: true, status: false, 'prof-startup': false, 'no-cached-data': false, 'prof-v8-extensions': false, 'disable-extensions': false, 'disable-gpu': false, 'disable-chromium-sandbox': false, sandbox: false, telemetry: false, debugRenderer: false, 'enable-smoke-test-driver': false, logExtensionHostCommunication: false, 'skip-release-notes': false, 'skip-welcome': false, 'disable-telemetry': false, 'disable-updates': false, 'use-inmemory-secretstorage': false, 'disable-workspace-trust': false, 'disable-crash-reporter': false, 'crash-reporter-id': '6e06c081-cd0e-4e62-a4a6-b1f4148a86aa', 'skip-add-to-recently-opened': false, 'unity-launch': false, 'open-url': false, 'file-write': false, 'file-chmod': false, force: false, 'do-not-sync': false, trace: false, 'preserve-env': false, 'force-user-env': false, 'force-disable-user-env': false, 'open-devtools': false, 'disable-gpu-sandbox': false, '__enable-file-policy': false, 'enable-coi': false, 'no-proxy-server': false, 'no-sandbox': false, nolazy: false, 'force-renderer-accessibility': false, 'ignore-certificate-errors': false, 'allow-insecure-localhost': false, 'disable-dev-shm-usage': false, 'profile-temp': false, logsPath: '/Users/xxx/Library/Application Support/Code/logs/20240924T105323' } [main 2024-09-24T08:53:23.612Z] Resolving machine identifier... [main 2024-09-24T08:53:23.612Z] Resolved machine identifier: 5d3ee6c5bb15e281e3b2a3b99f7e88cd7276f05de4b7832e9c232cb62ec36ec9 [main 2024-09-24T08:53:23.612Z] Main->SharedProcess#connect [main 2024-09-24T08:53:23.613Z] StorageMainService: creating application storage [main 2024-09-24T08:53:23.615Z] ElectronURLListener: waiting for window to be ready to handle URLs... [main 2024-09-24T08:53:23.615Z] lifecycle (main): phase changed (value: 2) [main 2024-09-24T08:53:23.615Z] windowsManager#open [main 2024-09-24T08:53:23.617Z] windowsManager#open pathsToOpen [ { workspace: { id: '4fcb0bf041acd7ab765c62b26ebb7a3f', uri: [v] }, type: 2, exists: true } ] [main 2024-09-24T08:53:23.617Z] windowsManager#doOpenFolderOrWorkspace { folderOrWorkspace: { workspace: { id: '4fcb0bf041acd7ab765c62b26ebb7a3f', uri: [v] }, type: 2, exists: true }, filesToOpen: undefined } [main 2024-09-24T08:53:23.617Z] IPC Object URL: Registered new channel vscode:de7e059e-60fe-416f-8f40-e672c36fe342. [main 2024-09-24T08:53:23.617Z] window#validateWindowState: validating window state on 2 display(s) { mode: 1, x: 2136, y: 156, width: 1122, height: 768 } [main 2024-09-24T08:53:23.638Z] window#validateWindowState: multi-monitor working area { x: 1920, y: 25, width: 1920, height: 1055 } [main 2024-09-24T08:53:23.638Z] window#ctor: using window state { mode: 1, x: 2136, y: 156, width: 1122, height: 768 } [main 2024-09-24T08:53:23.666Z] window#load: attempt to load window (id: 1) [main 2024-09-24T08:53:23.672Z] StorageMainService: creating workspace storage (4fcb0bf041acd7ab765c62b26ebb7a3f) [main 2024-09-24T08:53:23.672Z] windowsManager#open used window count 1 (workspacesToOpen: 0, foldersToOpen: 1, emptyToRestore: 0, emptyToOpen: 0) [main 2024-09-24T08:53:23.673Z] lifecycle (main): phase changed (value: 3) [main 2024-09-24T08:53:23.673Z] resolveShellEnv(): skipped (VSCODE_CLI is set) [main 2024-09-24T08:53:23.673Z] update#setState disabled [main 2024-09-24T08:53:23.673Z] update#ctor - updates are disabled by user preference [0924/105323.901862:WARNING:in_range_cast.h(38)] value -634136515 out of range [0924/105323.911810:WARNING:crash_report_exception_handler.cc(235)] UniversalExceptionRaise: (os/kern) failure (5) [0924/105323.947894:ERROR:directory_reader_posix.cc(42)] opendir /Users/xxx/Library/Application Support/Code/Crashpad/attachments/9614511b-9649-4956-aa1a-50ca6beaa55a: No such file or directory (2)

@deepak1556
Copy link
Collaborator

Thanks , the logs confirm there is a crash. Can you attach the most recent *.dmp file from ~/Library/Application\ Support/Code/Crashpad/completed

@jianbingfang
Copy link

Same issue, resolved by reinstalling vscode(v1.93.1)

@ungoldman
Copy link
Author

ungoldman commented Sep 24, 2024

confirmed resolved by downloading latest vscode from https://code.visualstudio.com/download and overwiting previous version in Applications, thanks @jianbingfang

@vs-code-engineering vs-code-engineering bot removed the info-needed Issue requires more information from poster label Sep 24, 2024
@deepak1556 deepak1556 added the info-needed Issue requires more information from poster label Sep 25, 2024
@Luis-Urso
Copy link

Upgraded mine to version 1.94.0 and the issue got solved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
info-needed Issue requires more information from poster
Projects
None yet
Development

No branches or pull requests

5 participants