VSCord cannot connect to Discord via RPC

[TomG07]

I've been having this problem for a few days now, and I can't find any solution...
This is the error that appears when I open VSCode:

This error appears in the logs:

What am I doing wrong?
Discord and VSCode are not running as Administrator...

[SlyTheFloof]

same issue here

[rushkii]

stop using this extension, this extension is so problematic, and the owner never care about the full of bugs 🤡

[amolinarius]

@rushkii This extension works very well and is often updated (last update was 2 days ago). I found that the bug was coming from Discord in #312, not from the extension, so the owner was obviously unable to do anything. Finally, it has more than 450k downloads on the marketplace. Why would 450k people choose an extension full of bugs ?

[rushkii]

@rushkii This extension works very well and is often updated (last update was 2 days ago). I found that the bug was coming from Discord in #312, not from the extension, so the owner was obviously unable to do anything. Finally, it has more than 450k downloads on the marketplace. Why would 450k people choose an extension full of bugs ?

it works on the first time I used this extension, but unfortunately, it's not working anymore, and I don't know how solve the error.
the extension iCrawl created is more stable and still works, why the discord-vscode works and this extension doesn't?

[xhayper]

stop using this extension, this extension is so problematic, and the owner never care about the full of bugs 🤡

Sorry, i am busy with college prep so i can't take care of this extension as much as before

[rushkii]

stop using this extension, this extension is so problematic, and the owner never care about the full of bugs 🤡

nvm, I tried on debug mode of vscord extension, it because of the button throwing error when the {git_url} is empty or invalid URL, I'm making a vscord settings generator so everyone should not face issues when using this extension.

[TomG07]

This still happen. Is there any update?

[yannouuuu]

Same here

[TomG07]

I found the origin of this error

• After a long time, I've tried many things and nothing worked.
• I've searched on my computer processes, and DIscord App had 2 main processes running, one of them was the correct one to be running, and the other (without child processes) was not suposed to be there.
• I closed this last one and restarted the Discord App and VScode app, and guess what, it worked.

[xhayper]

So, a zombie process caused all of this? wow... this issues and been puzzling everyone for many years now and it turns out to be a zombie process.... thank you so much for solving the mystery

[TomG07]

So, a zombie process caused all of this? wow... this issues and been puzzling everyone for many years now and it turns out to be a zombie process.... thank you so much for solving the mystery

Confirm if it worked for you so other people can solve this problem.

[yannouuuu]

I found the origin of this error

• After a long time, I've tried many things and nothing worked.
• I've searched on my computer processes, and DIscord App had 2 main processes running, one of them was the correct one to be running, and the other (without child processes) was not suposed to be there.
• I closed this last one and restarted the Discord App and VScode app, and guess what, it worked.

Btw what ghost process are you talking about? because they are all useful to discord TT

[TomG07]

I found the origin of this error

• After a long time, I've tried many things and nothing worked.
• I've searched on my computer processes, and DIscord App had 2 main processes running, one of them was the correct one to be running, and the other (without child processes) was not suposed to be there.
• I closed this last one and restarted the Discord App and VScode app, and guess what, it worked.

Btw what ghost process are you talking about? because they are all useful to discord TT

It seems like you don't have that one ghost process...

[JancoNel]

I mean , the extension worked fine for me until discord termed my account then it gave the same error until I logged in on the new acc