# Surely it's a bug that it 49.8gb for state.vscdb.backup and 50.54gb for state.vscdb

**URL:** <https://forum.cursor.com/t/surely-its-a-bug-that-it-49-8gb-for-state-vscdb-backup-and-50-54gb-for-state-vscdb/147615>\
**Category:** Bug Reports\
**Created:** [December 29, 2025, 7:23pm UTC](https://forum.cursor.com/t/surely-its-a-bug-that-it-49-8gb-for-state-vscdb-backup-and-50-54gb-for-state-vscdb/147615 "2025-12-29T19:23:17Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![esaruoho](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/esaruoho/32/37426_2.png) [@esaruoho](https://forum.cursor.com/u/esaruoho)\
**Post date:** [December 29, 2025, 7:23pm UTC](https://forum.cursor.com/t/surely-its-a-bug-that-it-49-8gb-for-state-vscdb-backup-and-50-54gb-for-state-vscdb/147615/1 "2025-12-29T19:23:17Z")

</div>

### Where does the bug appear (feature/product)?

Cursor IDE

### Describe the Bug

suddenly noticed that my macbookpro was running out of diskspace. then found that the state.vscdb.backup is 49.8gb and state.vscdb is 50gb. surely this is some sort of a leak?

### Steps to Reproduce

i just kept using cursor and suddenly 50gb+50gb state.vscdb.

### Expected Behavior

diskspace is not supposed to be eaten up like this

### Operating System

MacOS

### Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.44  
VSCode Version: 1.105.1  
Commit: 20adc1003928b0f1b99305dbaf845656ff81f5d0  
Date: 2025-12-24T21:41:47.598Z  
Electron: 37.7.0  
Chromium: 138.0.7204.251  
Node.js: 22.20.0  
V8: 13.8.258.32-electron.0  
OS: Darwin arm64 24.6.0

### For AI issues: which model did you use?

opus4.5

### Does this stop you from using Cursor

Yes - Cursor is unusable

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [December 29, 2025, 8:46pm UTC](https://forum.cursor.com/t/surely-its-a-bug-that-it-49-8gb-for-state-vscdb-backup-and-50-54gb-for-state-vscdb/147615/2 "2025-12-29T20:46:30Z")

</div>

Hey, thanks for the report. The issue where `state.vscdb` grows to 50+ GB is a known system-level issue in VS Code, and it can also affect Cursor since it’s a fork of VS Code.

This usually happens because of:

- Multiple workspace caches in `workspaceStorage` (each new window creates a new folder)
- Extensions creating huge index databases
- Junk building up in global settings

Before deleting anything, please export your Cursor profile:

- Settings `Cmd+,` → Profiles → Export Profile
- Save your settings, extensions, and keybindings

Then delete the bloated database:

```bash
rm ~/Library/Application\ Support/Cursor/User/globalStorage/state.vscdb*

```

Important: Your chats will NOT be lost. They’re stored per project in `workspaceStorage/<workspace-id>/state.vscdb`. Deleting `globalStorage/state.vscdb` only resets global UI settings, which you already exported.

After restart, Cursor will create a new clean global settings database.

I’ll pass this to the team. We likely need an automatic cleanup for old data and a disk usage warning.

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [January 20, 2026, 8:47pm UTC](https://forum.cursor.com/t/surely-its-a-bug-that-it-49-8gb-for-state-vscdb-backup-and-50-54gb-for-state-vscdb/147615/3 "2026-01-20T20:47:03Z")

</div>

Closed on January 20, 2026, 8:47pm UTC

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.