-
Notifications
You must be signed in to change notification settings - Fork 9.5k
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
Not enough memory resources are available to process this command #15217
Comments
Hi @gatorlanphear ! 👋 I'm not sure what this is about, but seems to happen when the app tries to store your GitHub user token in the Windows Credentials Manager. Could you try rebooting your machine and try again? Hopefully that's all you need 🤞 |
I have rebooted several times. It has not changed the result.
Is there another solution?
Gator
…On Thu, Sep 1, 2022 at 11:27 PM Sergio Padrino ***@***.***> wrote:
Hi @gatorlanphear <https://github.com/gatorlanphear> ! 👋
I'm not sure what this is about, but seems to happen when the app tries to
store your GitHub user token in the Windows Credentials Manager. Could you
try rebooting your machine and try again? Hopefully that's all you need 🤞
—
Reply to this email directly, view it on GitHub
<#15217 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A2ZDE5BFUDLSHOUPNIRTCR3V4GM55ANCNFSM6AAAAAAQCX62ME>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Another report on the subject: #15226 |
I deleted an older credential to make space for github credentials.
…On Sun, Sep 4, 2022 at 3:46 PM Gator Lanphear ***@***.***> wrote:
I have opened the credential manager and I do NOT have any listing for
GitHub.
Solutions?
Gator
On Sun, Sep 4, 2022 at 1:34 PM Tsvetilian Yankov ***@***.***>
wrote:
> Another report on the subject: #15226
> <#15226>
> The context is the same... the error appears when GitHub Desktop tries to
> save the credentials in the credential manager. Could you check if you have GitHub
> - {your_github_url} in your credential manager (open search > search for
> "Credential Manager" > Windows Credentials)? Also, in #12712
> <#12712>, running GitHub
> Desktop as admin fixed the issue.
>
> —
> Reply to this email directly, view it on GitHub
> <#15217 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/A2ZDE5E3HHQDTU2DNCOUDMDV4UBVLANCNFSM6AAAAAAQCX62ME>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
I do not have GitHub - anything in Credential Manager and it does not work if run as administrator. |
It looks like the issue is related to too many entries in Windows Credential Manager. At some point the os calls Could you try to run |
I was able to delete a credential and it worked! Thanks for your help!
…On Mon, Sep 5, 2022 at 6:01 AM Tsvetilian Yankov ***@***.***> wrote:
It looks like the issue is related to too many entries in Windows
Credential Manager. At some point the os calls CredWrite and it fails
with ERROR_NOT_ENOUGH_MEMORY 😞 Visual Studio Code has the same issue in
the "Troubleshooting keychain issues"
<https://code.visualstudio.com/docs/editor/settings-sync#_troubleshooting-keychain-issues>
section of its docs. Some users report that it works properly once they
remove some of the entries in the Credential Manager.
Could you try to run cmdkey /list to see how many entries you have?
—
Reply to this email directly, view it on GitHub
<#15217 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A2ZDE5EWSUPIJKHGP6FMJDLV4XVJFANCNFSM6AAAAAAQCX62ME>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
it worked but I've had to delete production credentials to make it work. It won't last. |
¡Pude eliminar una credencial y funcionó! ¡Gracias por tu ayuda bro! |
I have opened the credential manager and I do NOT have any listing for
GitHub.
Solutions?
Gator
…On Sun, Sep 4, 2022 at 1:34 PM Tsvetilian Yankov ***@***.***> wrote:
Another report on the subject: #15226
<#15226>
The context is the same... the error appears when GitHub Desktop tries to
save the credentials in the credential manager. Could you check if you have GitHub
- {your_github_url} in your credential manager (open search > search for
"Credential Manager" > Windows Credentials)? Also, in #12712
<#12712>, running GitHub Desktop
as admin fixed the issue.
—
Reply to this email directly, view it on GitHub
<#15217 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A2ZDE5E3HHQDTU2DNCOUDMDV4UBVLANCNFSM6AAAAAAQCX62ME>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
This solution always work for me. Go to Control Panel -> User Accounts -> Manage your credentials -> Windows Credentials Before do anythings below, please do not forget Back up Credentials to make sure you did not remove important credentials accidentally. After backed up then remove unnecessary or no longer use credentials such as mapping drive, credentials related to old software that you've uninstalled, etc. This way help to free up space of Credentials Manager. Try to open Github Desktop and see if the problem has been gone to the wind. If yes, congratuation and you will see "Github - https://....." on Generic Credentials |
Again solved by deleting tons of credentials. About 100+ starting with XblGrts in my case. Now Roblox Studio also logs in properly. Is bizarre that so many apps are relying on this feature that clearly doesn't work. |
It works if you delete some old credentials. As others mentioned, there is probably an error with older credentials existing and then it throws an automatic error. I did not have to run the application in admin. I did not have to reboot the computer. I just deleted some credentials :) |
The problem
I try to "Sign in to your GitHub.com account to access your repositories." from the desktop app, I am sent to the browser to "continue with browser" to sign in.
And I get an error code and cannot sign in.
Release version
3.07 (x64)
Operating system
Win 11
Steps to reproduce the behavior
Log files
2022-09-01.desktop.production.log
2022-09-01.desktop.production.log
Screenshots
Additional context
No response
The text was updated successfully, but these errors were encountered: