Frequent Freezes in Cursor AI IDE - Any Solutions?

Exact Same Issues
My system:

Version: 0.47.8 (Universal)
VSCode Version: 1.96.2
Commit: 82ef0f61c01d079d1b7e5ab04d88499d5af500e0
Date: 2025-03-18T05:28:47.245Z
Electron: 32.2.6
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Darwin arm64 24.3.0

P.S. I’ve downgraded to 0.46,

Also I don’t know why but on suggested update by cursor is displayed v0.48, but after the update goes to 0.47.8, really hope that issue will be fixed in 48

Still having the same issue, even on 1.0 it doesn’t work anywhere near as well as on 0.46. Created my own post to try to get some support, but nothing helpful yet :frowning:

1 Like

@ajmeese7 I had the same issue, tracked it down to state.vscdb freezing my whole PC when being updated. My process monitor was showing massive writes to that sqlite3 database, even when it was only couple of MB with size it was still crippling a 16core 7950x with 128GB RAM… What I did was moved it to tmp and made an autostart script that copies the database file to /tmp which is stored in RAM memory and periodically does a backup where the original file is stored. I don’t encounter any freezes at all now.

Below is the script made with Cursor haha

#!/bin/bash

Source and destination paths

BACKUP_DIR=“$HOME/.config/Cursor/User/globalStorage”
SOURCE_FILE=“${BACKUP_DIR}state.vscdb”
TEMP_DIR=“/tmp/cursor_state”
TEMP_FILE=“$TEMP_DIR/state.vscdb”
BACKUP_FILE=“$BACKUP_DIR/state.vscdb_backup”

Function to create backup

create_backup() {
# Create backup directory if it doesn’t exist
mkdir -p “$BACKUP_DIR”

# Create backup with timestamp
backup_file="$BACKUP_DIR/state.vscdb_backup"

# Copy the temp file to backup location
cp "$TEMP_FILE" "$backup_file"
echo "Backup created: $backup_file"

}

Create temp directory if it doesn’t exist

mkdir -p “$TEMP_DIR”

Check if backup exists and use it, otherwise use original file

if [ -f “$BACKUP_FILE” ]; then
echo “Using existing backup file”
cp “$BACKUP_FILE” “$TEMP_FILE”
else
# Check if source file exists
if [ ! -f “$SOURCE_FILE” ]; then
echo “Error: Neither backup nor source file exists”
exit 1
fi
echo “Using original source file”
cp “$SOURCE_FILE” “$TEMP_FILE”
fi

Remove existing symlink if it exists

if [ -L “$SOURCE_FILE” ]; then
rm “$SOURCE_FILE”
fi

Create symlink

ln -s “$TEMP_FILE” “$SOURCE_FILE”

echo “Cursor state file has been moved to $TEMP_FILE and symlinked”

Start backup loop in background

while true; do
create_backup
sleep 600 # Sleep for 10 minutes
done &

2 Likes

Constantly freezing on Linux… seems to be linked to the amount of time it’s been running, or quite possibly the length of a conversation in progress. Longer conversations lag up the editor more. (yes I know it culls past a few past messages, but still seems linked)

1 Like

AI Editor is just unusable, it constantly freezes whenever I focus it. What a garbage piece of software.

It’s consuming a lot of hard drive, When working with fast ai like Claude 3.7 sonnet,it uses the hard drive to full potential 95% active time, I don’t know if it because it is creating backups or what. But that is my case, ram and CPU is okey.

Having same issue, even as i type the prompt if ofter freezes for a few seconds, and when switching in Windows between apps its a sure thing IDE will take 10-20 seconds to show up & unfreeze. Any help how to identify the issue ?

I’ve noticed that Cursor AI sometimes gets stuck processing a request for more than 20 seconds. There are no internet connectivity issues, and my system is working fine. This seems to happen intermittently and affects productivity. Has anyone else experienced this, or is there a known fix or explanation?

Which OS and Cursor versions are you using?

My setup is a MacBook Pro (M1 Pro, 16 GB RAM).

  1. Can you please check in Cursor > Help > Process Explorer

  2. Do you have any long chat open? (if yes open new chat to see if that unfreezes)

  3. Are any processes running in terminal? e.g. tests or CLI commands?

It would show what is consuming CPU or Ram heavily to cause freezes. Its not a frequent issue so eliminating causes is the best way.


No long chats involved. I checked Activity Monitor — it’s not consuming much RAM. As shown in the attached screenshot, it’s stuck at this point. The only workaround is to stop and re-run the request.

So the freeze is NOT Cursor freezing but the Agent freezing?

yes

OK thats a different case and topic. Could you please file a full separate bug report so this can be investigated in detail? If possible please attach Request ID there.

sure.

1 Like