You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 15, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on May 15, 2026. It is now read-only.
Extension crashes and performance issues due to excessive globalState usage for task history #3784
The current task history persistence mechanism stores all history items directly in VSCode's globalState, which is causing several critical issues:
VSCode Warnings: The extension triggers VSCode warnings about excessive globalState usage:
WARN [mainThreadStorage] large extension state detected (extensionId: RooVeterinaryInc.roo-cline, global: true): 6173.2822265625kb. Consider to use 'storageUri' or 'globalStorageUri' to store this data on disk instead.
Extension Crashes and UI Issues: Users experience various issues that may be related to memory management and globalState limitations:
Complete extension crashes or grey/white screens
Memory leaks consuming all available RAM
Possible globalState race conditions between VS Code instances leading to hangs, crashes, and VS Code instability
Performance Degradation: Even before crashing, the extension suffers from performance issues due to loading and processing large amounts of history data at once.
globalState Thrashing: The current implementation loads and replaces the entire array of task history items in globalState every time a single task is created or modified. This causes:
Excessive memory usage as the entire array is loaded into memory
Significant performance overhead for each task operation
Potential race conditions when multiple operations attempt to modify the array simultaneously
Increased risk of data corruption if a write operation is interrupted
Unnecessary network/disk I/O as the entire state is serialized and persisted repeatedly
Scale Problem: A busy developer can accumulate tens of thousands of tasks over the course of a year. At this scale, the globalState approach becomes completely unsustainable:
The size of the globalState can grow to many megabytes
Loading and processing this amount of data becomes increasingly slow
The likelihood of crashes and performance issues increases dramatically
VSCode's globalState was never designed to handle this volume of data
I may have a related symptom having 253 tasks in my state.vscdb SQLite database. The extension server crashed and none of Roo Code's UI worked. I removed tasks from state.vscdb and Roo Code started to work, for some time, but eventually the extension server crashed again. After only leaving 50 tasks there, everything works again.
I may have a related symptom having 253 tasks in my state.vscdb SQLite database.
interesting, note to self: sqlite3 ~/.config/Code\ -\ Insiders/User/globalStorage/state.vscdb "SELECT json_extract(value, '$.taskHistory') FROM ItemTable WHERE key='RooVeterinaryInc.roo-cline'"
The extension server crashed and none of Roo Code's UI worked. I removed tasks from state.vscdb and Roo Code started to work, for some time, but eventually the extension server crashed again. After only leaving 50 tasks there, everything works again.
That has been addressed by #3785 which has not yet been merged yet, hopefully soon. I will post a .VSIX when the translations are complete hopefully later today.
Activity
akaihola commentedon Jun 26, 2025
I may have a related symptom having 253 tasks in my
state.vscdbSQLite database. The extension server crashed and none of Roo Code's UI worked. I removed tasks fromstate.vscdband Roo Code started to work, for some time, but eventually the extension server crashed again. After only leaving 50 tasks there, everything works again.KJ7LNW commentedon Jun 26, 2025
interesting, note to self:
sqlite3 ~/.config/Code\ -\ Insiders/User/globalStorage/state.vscdb "SELECT json_extract(value, '$.taskHistory') FROM ItemTable WHERE key='RooVeterinaryInc.roo-cline'"That has been addressed by #3785 which has not yet been merged yet, hopefully soon. I will post a .VSIX when the translations are complete hopefully later today.