Skip to content

Performance: Large globalState TaskHistory arrays cause multi-vscode-instance hangs #5330

@KJ7LNW

Description

@KJ7LNW

Version: v3.22.5
API Provider: anthropic
Model: sonnet-3.5

This issue will be fixed by PR #3785.

What happened?

Large globalState TaskHistory arrays are causing multi-vscode-instance process hangs that get stuck for 5-30 seconds. The following error is consistently reported:

Image

log.ts:450  WARN [mainThreadStorage] large extension state detected (extensionId: RooVeterinaryInc.roo-cline, global: true): 9979.3125kb. Consider to use 'storageUri' or 'globalStorageUri' to store this data on disk instead.
warn @ log.ts:450
log.ts:440  INFO Extension host (LocalProcess pid: 435346) is unresponsive.
localProcessExtensionHost.ts:279 Extension Host
localProcessExtensionHost.ts:280 Debugger attached.
log.ts:440  INFO UNRESPONSIVE extension host: starting to profile NOW
log.ts:440  INFO Extension host (LocalProcess pid: 435346) is responsive.

Expected behavior

TaskHistory should be stored efficiently to prevent VSCode from hanging, and the extension state should not grow to excessive sizes.

Steps to reproduce

  1. Use Roo Code extensively, creating many tasks
  2. Open multiple VSCode instances with Roo Code extension
  3. Observe periodic hangs of 5-30 seconds
  4. Check the logs for the large extension state warning

Additional context

This issue will be solved by PR #3785 which addresses the storage of TaskHistory data.

Metadata

Metadata

Assignees

Labels

Issue - In ProgressSomeone is actively working on this. Should link to a PR soon.bugSomething isn't working

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions