-
Notifications
You must be signed in to change notification settings - Fork 27.9k
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
feat: provide disable-chromium-sandbox runtime argument #186004
Conversation
src/vs/workbench/contrib/relauncher/browser/relauncher.contribution.ts
Outdated
Show resolved
Hide resolved
src/vs/workbench/contrib/relauncher/browser/relauncher.contribution.ts
Outdated
Show resolved
Hide resolved
src/vs/workbench/contrib/relauncher/browser/relauncher.contribution.ts
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If I can make a suggestion: lets drop the changes that trigger a restart dialog for argv.json
from this PR. Users that are impacted of the sandbox issue already need to start VS Code with --no-sandbox
to even be able to start it and its fine for them to leave VS Code running even after changing argv.json
. Asking them to restart again is a strange experience I would argue.
src/vs/workbench/contrib/relauncher/browser/relauncher.contribution.ts
Outdated
Show resolved
Hide resolved
src/vs/workbench/contrib/relauncher/browser/relauncher.contribution.ts
Outdated
Show resolved
Hide resolved
…6004) * feat: provide disable-chromium-sandbox runtime argument * chore: address review feedback * chore: remove relaunch prompt
Addresses #184687 (comment)
Users should now be able to persist their sandbox preference via,