8000 [Critical] Checkpointing Blob files or something blow up in size - Dangerous if not checked · Issue #2308 · RooVetGit/Roo-Code · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[Critical] Checkpointing Blob files or something blow up in size - Dangerous if not checked #2308

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
DKEQ opened this issue Apr 5, 2025 · 4 comments
Open

[Critical] Checkpointing Blob files or something blow up in size - Dangerous if not checked #2308

DKEQ opened this issue Apr 5, 2025 · 4 comments
Labels
bug Something isn't working needs scoping Needs up-front scoping to be actionable

Comments

@DKEQ
Copy link
DKEQ commented Apr 5, 2025 •
edited
Loading

App Version

3.11.6

API Provider

VS Code LM API

Model Used

Claude 3.5 Sonnet

Actual vs. Expected Behavior

Actual

Checkpoint blobs balloon, causing excessive disk space loss (Max recorded was >370GB lost)

Expected

Blobs only grow proportional to chat size and not that big.

Detailed Steps to Reproduce

  1. Turn Checkpointing on
  2. Use Roo
  3. Especially use Roo With Boomerang mode on
  4. Ensure you're on the latest Roo Code Version
  5. Code anything, and you should see the text file size indicator quickly reach 1 GB, 5GB, 10GB>

Relevant API Request Output

[Not an API Problem]

Additional Context

Exhibit A

Image

Exhibit B

Image

Exhibit C

Image

I have effectively lost all of my chats because I had to delete close to 400GB worth of checkpoint data. If I wasn't paying attention, my SSD would have choked. Please fix this. 🙏
@DKEQ DKEQ added the bug Something isn't working label Apr 5, 2025
@hannesrudolph hannesrudolph moved this from New to Issue [Needs Scoping] in Roo Code Roadmap Apr 7, 2025
@hannesrudolph hannesrudolph added the needs scoping Needs up-front scoping to be actionable label Apr 7, 2025
@mrubens
Copy link
Collaborator
mrubens commented Apr 7, 2025

Ugh sorry about that! Do you have any idea which files were causing the size to balloon? cc: @cte

@DKEQ
Copy link
Author
DKEQ commented Apr 8, 2025

I didn't get a chance to see exactly which files were causing it before i deleted the task folders and disabled checkpoints at the time, but they were located in the objects folder.

My hunch is: the longer convos go on for, when swtiching to subtasks, the more the checkpoint data gets multiplied to keep the context whether intentionally or unintentionally.

Plus because subtasks are not temporary and with how many subtasks get created, especially with boomerang mode, it can quickly get out of hand when working on big projects.

@DKEQ
Copy link
Author
DKEQ commented Apr 15, 2025

It appears checkpoints have been fixed? is it safe to close this or is it still not finished?

Image

@limingchina
Copy link

I have a large repository and ends up with many checkpoints, each with 4-5G! Is it doing a full gitclone?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working needs scoping Needs up-front scoping to be actionable
Projects
Roo Code Roadmap
Status: Issue [Needs Scoping]
Milestone
No milestone
Development

No branches or pull requests
4 participants
@mrubens @limingchina @hannesrudolph @DKEQ
0