-
Notifications
You must be signed in to change notification settings - Fork 235
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
extension not working #818
Comments
I have been having this issue on and off for a while. Whatever causes it also seems to leave orphan VSCode code chunklets running that will make sure it doesn't work and also helpfully leaves behind dysfunctional cached code chunks that will make sure it will continue to not work, even if you reboot! In Ubuntu, this fixes it for me. I don't use Windows or OS X.
Check for Leftovers: $ pgrep -l code-insider
612285 code-insiders
612294 code-insiders
...and so forth, on and on.
GOTO Check for Leftovers. No Leftovers:
END. |
Thank you! |
And killing the stray processes and removing the cached data worked on Windows? |
Yep, killing all code processes first, then removing the cached data, worked on Windows 👍 |
@mhutchie Would you like a pull request to add a markdown file with these instructions tweaked up for Linux and Windows if @clegendre could help with that part? I don't use OS X any more, so, even though it's pretty Linux compatible-ish, I can't test the instructions there. |
Bug Description:
In VsCode git graph extension when i try to open the extension it is not opening. i tried to enable and disable the extension multiple times but still getting the same issue . even after uninstalling and installing the extension several times again still getting the same issue at least provide a good understandable error message if something is wrong from my side .
Steps to reproduce the behaviour:
Expected Behaviour:
should open after enabling and disabling multiple times
Environment
⚠ Please make sure you complete all of the required sections of this template. Without this required information, it will be harder to replicate this bug, and cause additional delays in resolving it.
The text was updated successfully, but these errors were encountered: