`Cursor is not responding` / `The window is not responding` Issues

damag · May 27, 2025, 7:54pm

Hello, when using Cursor version 0.50.7 on my main Linux workstation, the application constantly freezes with a “Cursor Is Not Responding” message.
I’ve tested it on a Windows laptop and I don’t have this problem, so it seems to be particular to Linux (maybe?)…

I did notice when this happens that the disk lights go crazy, and running a system monitor on the side confirms that it is writing to disk when it freezes.

Digging a bit more I ran this command to see where Cursor was writing:

$ sudo fatrace -c --command=cursor

And when the freezes occur I see many lines writing to ~/.config/Cursor/User/globalStorage/state.vscdb-journal

Having read some other posts mentioning that it may be due to my state.vscdb getting too large, I tried completely removing ~/.config/Cursor but the problem persists even with an 8 MB file. So that didn’t fix the issue for me.

This issue does stop me from using Cursor as it makes it basically unusable, and unfortunately I will have to cancel my subscription if I can’t get this issue resolved.
I do also have vscode installed on this same Linux machine and I never ran into this issue.

Any ideas?

Hooshu · May 28, 2025, 4:58am

I am having the same issue. I had to downgrade to a previous installation I had since I couldn’t work with all the freezes.

damag · May 28, 2025, 6:57pm

Which version of Cursor doesn’t freeze for you? I forgot to mention but for me it didn’t just start with 0.50.7, it seems that it’s been doing it for quite a few versions already.

slyyyle · May 28, 2025, 7:34pm

I think this has to do with Wayland and GPU interaction. If the program sits open for more than 10 minutes, it triggers that dialog due to some sort of interrupt logic and then doesn’t stop. It seems environment or process based, and not related to chat history. That being said, there is actually no measurable way to know the seemingly most important things you need to know to interact intelligently with the models. Context window, cost per token (seriously?), a simple rudimentary SWAG analysis given past conversations or average conversation metadata stored by Cursor, which models are interacting where, how Auto mode works, why they don’t communicate Auto mode is by design a massive pitfall for architecture, none of it makes sense. AI is hard. Most people’s gripes - have nothing to do with AI. Cursor is VS Code + requests + optim. If I’m double paying in some nebulous way for this service, they need to re-evaluate their business model. I understand users educating themselves, but I also understand how easy the middle ground is and why it isn’t being taken.

Also this has been an issue since mid-2024, they just refuse to take ownership of it.

damag · May 28, 2025, 10:00pm

The issue seems to come from recent minor versions of the SQLite library. With the latest SQLite 3.49.2 installed Cursor freezes non-stop, but I tried downgrading one minor version at a time and SQLite 3.49.0 seems to resolve the problem for me.

From my quick testing, that means this issue was introduced in SQLite 3.49.1. But based on the release notes for this minor patch, I don’t see any obvious reasons.

Changes in this specific patch release, version 3.49.1 (2025-02-18):

Improve portability of makefiles and configure scripts.

Fix a bug in the concat_ws() function, introduced in version 3.44.0, that could lead to a memory error, specifically a write past the end of allocated space, if the separator string is larger than two megabytes.

Enhanced the SQLITE_DBCONFIG_LOOKASIDE interface to make it more robust against misuse.

Maybe the Cursor dev team could take a look at why this might be happening because once other operating systems start upgrading to more recent versions of SQLite, more people may start having this problem… Let me know if I can provide any more info to help out.

damag · May 29, 2025, 7:20am

After more testing, although it seems a bit better with SQLite 3.49.0, I still get the freezes while Cursor is doing lots of writes to ~/.config/Cursor/User/globalStorage/state.vscdb-journal

So it seems this isn’t the solution after all…

opdoeq · May 29, 2025, 8:48am

Can confirm this makes cursor unusable.

Hooshu · May 30, 2025, 3:42pm

I am currently using this with no issues:

Version: 0.48.9
VSCode Version: 1.96.2
Commit: 61e99179e4080fecf9d8b92c6e2e3e00fbfb53f0
Date: 2025-04-12T19:09:41.045Z
Electron: 34.3.4
Chromium: 132.0.6834.210
Node.js: 20.18.3
V8: 13.2.152.41-electron.0
OS: Linux x64 6.8.0-58-generic

I have no idea if 0.49 works as I have not tried.

blen2r · May 31, 2025, 5:05pm

I can corroborate, I get the same issue. It’s a weird freezing issue, sometimes the UI still refreshes as I can see chat lines coming in and my keyboard cursor blinking, but my mouse cursor is frozen and I can’t click on anything.

Edit: as a test, while Cursor was frozen, I deleted ~/.config/Cursor/User/globalStorage/state.vscdb and Cursor immediately started working again.

opdoeq · June 4, 2025, 6:33am

seems to be more stable on xorg session

nmarseaud · June 5, 2025, 3:54pm

Edit: as a test, while Cursor was frozen, I deleted ~/.config/Cursor/User/globalStorage/state.vscdb and Cursor immediately started working again.

Can confirm, thanks for the heads up. Just updated to 1.0.0 and got the freeze on startup, deleting that file fixed it for me. Just had to re-log and re-setup.

ahhhh · June 5, 2025, 4:36pm

Same. Except the file reappeared/created and how I’m facing the issue again. It really makes Cursor unusable.

opdoeq · June 6, 2025, 11:33am

freezes a lot on xorg anyway but less than on wayland

JohnRickSanchez · June 9, 2025, 12:00pm

I had the same experience as you. Delete that file as it was at some point 300MB and it was crippling my PC completely. I solved it since then by moving that file to /tmp which is RAM memory based. I added a script to my autostart that handles it moving to /tmp and backing up periodically. The freezing has completely disappeared for me. Hope that helps

#!/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 &

opdoeq · June 9, 2025, 5:16pm

it freezes even when opening the app please fix

flywhc · June 10, 2025, 4:06pm

The cursor was freezing with a popup ‘The Window not responding’ a few times recently. I had to click on reopen to get it working again.

I guess I got the way to reproduce the issue: ask cursor to generate code and frequently press CTRL-V in the chat window.

I am using Cursor pro subscription on Windows 11 pro (24H2 26100.4202)
Version: 1.0.0 (user setup)
VSCode Version: 1.96.2
Commit: 53b99ce608cba35127ae3a050c1738a959750860
Date: 2025-06-04T19:44:25.253Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100

flywhc · June 11, 2025, 1:54pm

I just got another freezing when I copied javascript logs from Edge Dev Tool console into the cursor chat window.

– I just realized that the log I pasted from Edge Dev tool was big - about 20MB.

jokerfool · June 11, 2025, 4:34pm

Start a new chat, this is happening because your chat is too big.

Go here to manage your chat history and delete.

AppData\Roaming\Cursor\User\workspaceStorage

Remember to backup first

Tosinkoa · June 11, 2025, 7:29pm

Please, kindly look into this issue. It’s extremely frustrating. The UI keeps freezing, and I constantly see the message: "Cursor (1.0.0)" is not responding.
This error makes the app completely unusable, even as a premium user.
Please help fix this. It has been a serious problem for a very long time, and it still hasn’t been addressed.

danperks · June 11, 2025, 8:26pm

Hey, can you share what version and OS you are on?

Also, did this work in a past version or has Cursor always done this?

Topic		Replies	Views
App Not Responding When AI is Generating Output Bug Reports	3	172	June 3, 2025
Why does Cursor stop responding? Bug Reports	1	50	April 26, 2025
Unresponsive window after update Bug Reports	19	492	June 20, 2025
The window is not responding error Bug Reports	9	1871	April 28, 2025
Cursor freezes every few seconds Bug Reports	13	533	April 14, 2025