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

Crashes upon launching, "perforce: invalid configuration" #117082

Closed
chloesheen opened this issue Feb 19, 2021 · 10 comments
Closed

Crashes upon launching, "perforce: invalid configuration" #117082

chloesheen opened this issue Feb 19, 2021 · 10 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s) info-needed Issue requires more information from poster macos-big-sur

Comments

@chloesheen
Copy link

  • VS Code Version: 1.53
  • OS Version: MacOS Big Sur 11.1

Steps to Reproduce:

  1. uninstalled previously crashing VSCode (deleted .NET, mono. etc following the support article)
  2. reinstalled latest version 1.53, opened it, crashes immediately with "Perforce: invalid configuration" message (screen recording attached)
vscode.crash.mov

Does this issue occur when all extensions are disabled?: Yes/No
I uninstalled and reinstalled, so the "code" command doesn't work anymore.

@IllusionMH
Copy link
Contributor

/needsMoreInfo

Does it happen if you launch code from CLI as code --disable-extensions?
Does it happen if you try to launch Insiders build? https://code.visualstudio.com/insiders/

@chloesheen
Copy link
Author

  1. It still crashes using code --disable-extensions
  2. launching Insiders build seems to be working fine. Is this my only option, or is there a way to repair VSCode on my machine?

Thanks!

@deepak1556
Copy link
Collaborator

Does it crash when you start with code --user-data-dir /tmp/vscode ?

launching Insiders build seems to be working fine

Insiders version will get promoted to stable at the end of every iteration. So you would get the fix in version 1.54. But to confirm if this is not an issue with settings cache, please try the above.

@chloesheen
Copy link
Author

Yup, still crashes that way.

@deepak1556
Copy link
Collaborator

@chloesheen
Copy link
Author

@deepak1556
Copy link
Collaborator

Thanks for the report, its a SIGABRT from the vscode-encrypt module same as #116690 . The module is mainly used for storing authenticated credentials from extensions, settings sync, proxy auth. Starting with a new data dir should eliminate settings sync and proxy auth as potential cause.

Can you also check if it crashes with a new user data dir and disabling extensions, code --user-data-dir /tmp/vscode-new --disable-extensions ,

@deepak1556
Copy link
Collaborator

Additionally can you confirm if you had enabled settings sync or performed authentication with any extension ?

Merging to #116690

@deepak1556 deepak1556 added the *duplicate Issue identified as a duplicate of another issue(s) label Feb 25, 2021
@chloesheen
Copy link
Author

Thanks, it still crashes with --user-data-dir /tmp/vscode-new --disable-extensions. I did use the remote ssh extension which required authentication.

@github-actions github-actions bot locked and limited conversation to collaborators Apr 11, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s) info-needed Issue requires more information from poster macos-big-sur
Projects
None yet
Development

No branches or pull requests

4 participants
@deepak1556 @IllusionMH @chloesheen and others