AgentArmorHQ
Sign in
  • AgentArmor teamTeam4d agoNeeds helpSolved

    Roo-Code makes VS Code go grey/blank — how do I recover and what causes it?

    Roo-Code 3.11.3 on VS Code 1.97.2 (Windows 10; also reported on macOS and Linux) turns the whole editor grey/blank, often while the model is thinking or applying a diff, and the window only comes back after reloading VS Code. No error message appears; the developer console shows repeated warnings about large Roo extension state (~1.4 MB). Is there a fix or a reliable recovery/workaround?

    Originally asked on GitHub: https://github.com/RooCodeInc/Roo-Code/issues/2270

    5 answers

    • Best answerAgentArmor teamTeam4d ago

      This bug is still unresolved — the GitHub issue was closed as a duplicate with no fix. A maintainer said there is no reliable way to reproduce it yet and no logs indicate the problem.

      Workaround that works:

      • Press Ctrl+Shift+P (Cmd+Shift+P on macOS) and run Reload Window. The editor comes back, but active extension state is reset (the current chat/task state may be lost).

      Diagnostic steps a maintainer asked for:

      • Help > Toggle Developer Tools > Console, then set the log level to All levels so nothing is filtered, and look for backtraces.
      • In the thread, the console showed entries like: WARN [mainThreadStorage] large extension state detected (extensionId: RooVeterinaryInc.roo-cline, global: true): 1414.6953125kb and a large Copilot file (commandEmbeddings.json, 25 MB). These are suspicious but not confirmed as the root cause.

      What is known from the thread:

      • Happens with both the normal API and the Copilot API, roughly every 30–60 minutes.
      • Appears related to apply_diff only because that shows a split diff view; the relevant console line was inlineDiffDeletedCodeMargin.ts:108 [Violation] 'requestIdleCallback' handler took 104ms.
      • Occurs across VS Code stable and Insider on Windows, Linux, and macOS, and with multiple windows/instances open.

      General advice: keep the developer console open when the grey screen appears and save the log output; a maintainer explicitly asked for those logs to pin down the cause.

      Did this work for you?
    • AgentArmor teamTeam4d ago

      What a GitHub user tried on GitHub (Worked)

      Reporter reloaded the whole VS Code window after the grey screen appeared; the editor came back, but only until the next occurrence.

      Source: https://github.com/RooCodeInc/Roo-Code/issues/2270 (opens external site)

      Did this work for you?
    • AgentArmor teamTeam4d ago

      What @KJ7LNW tried on GitHub (Worked)

      Maintainer suggested opening Help > Toggle Developer Tools > Console, switching to "All levels", then running Ctrl+Shift+P > Reload Window. The reload fixes the blank screen but resets extension state.

      Source: https://github.com/RooCodeInc/Roo-Code/issues/2270#issuecomment-2802903200 (opens external site)

      Did this work for you?
    • AgentArmor teamTeam4d ago

      What @appscaptain tried on GitHub (Didn't work)

      User waited for the model to finish, restarted VS Code, reopened the chat, and resumed the task; the grey screen returned while the next terminal command was being typed.

      Source: https://github.com/RooCodeInc/Roo-Code/issues/2270#issuecomment-2798522796 (opens external site)

      Did this work for you?
    • AgentArmor teamTeam4d ago

      What @NightOwlCoder tried on GitHub (Outcome unclear)

      User checked the developer console and found repeated VS Code warnings about large Roo extension state (about 1414 KB) plus a large Copilot commandEmbeddings.json file, but no crash backtrace.

      Source: https://github.com/RooCodeInc/Roo-Code/issues/2270#issuecomment-2860680457 (opens external site)

      Did this work for you?

    Add your answer or comment