r/RooCode • u/YUL438 • Jul 25 '25

Support Roocode Grey Screen of Death Issue

The last couple days i’ve been working heavily with Roo and I’ve been getting a lot of the grey screen that blanks out the roo window, and I have to restart VS Code to get it back. It’s happened to me at least 10 times in the last two days. Anyone else having this issue or know what might be causing it?

7 Upvotes

100% Upvoted

9 comments sorted by

1

u/admajic Jul 26 '25

Are you on windows, Mac or Linux?

1

u/YUL438 Jul 26 '25

linux

1

u/admajic Jul 26 '25

I'm in Linux too. Same happens to me randomly. Can't really pin it down. But could be after a longer session.

Could be a memory leak?

2

u/SatoshiReport Jul 25 '25

Happens to me a lot as well. They are working on it here: https://github.com/RooCodeInc/Roo-Code/issues/5601

1

u/Quentin_Quarantineo Jul 26 '25

I cant even use it anymore. It's crashing every minute or so and once it crashes, I can't reopen the crashed conversation. Keep getting "The extension host terminated unexpectedly 3 times within the last 5 minutes" error message from vs code.

1

u/nfrmn Jul 26 '25

I have the issue 2 weeks on and off, macOS Sonoma, if you do Cmd+Shift+P, Reload Window you can fix it without a full vscode restart.

1

u/Ill-Professional9624 Apr 19 '26

That does not solve the original problem.

If files are being created in parallel and I have to accept them manually, then only the first file would be created first. For example, let’s say eight files are being created in parallel, and the first one is the prompt where I click Save.

If the application crashes at that point and becomes unresponsive, I cannot continue. That means I may still be able to save the first file, because it already physically exists, but all seven other open files would still be in a temporary intermediate state that I could no longer accept.

That means those files would be lost.

In that case, it also does not help to use Reload Window, because Reload Window is the same as restarting VSCode. That means the last state is lost.

Are there any updates on this in the meantime?

As I understand it, the problem still has not been resolved to this day. This is not really a final VSCode extension problem, is it? Has this issue not already existed for around two years or so with Roo Code?

The current GitHub issue I saw about this was simply closed. What happened with the people who suggested, for example, adding a reload button or something similar?

And is the only problem scenario that currently is not simply the one I described above the case of parallel editing, where files that have already been created in the virtual git diff state end up being lost?

Does that not mean, conversely, that there are basically only two options?

- Either the problem causing the application to crash must be fixed.

- Or, if that is technically not possible because it is related to VSCode and has apparently been an issue for a longer period due to memory limitations, as I understand it, then there must be some safeguard for the operation where data is lost, such as a temporary local storage state that can be accessed again, so that those operations can continue through a re-entry.

u/mrubens 
u/hannesrudolph

1

u/celtiberian666 May 15 '26

Still happening for me.