Cursor latest version UI issues

Bug Reports
1

Describe the Bug

Cursor is having serious UI issues at our company to the point that we’re considering dropping it. This seems related to the length of the current chat, not number of chat histories, at least as far as I can tell. I’m guessing there’s excessive processing of something like rendering the entire chat or something along those lines. It’s almost impossible to work once you get to this stage.

Steps to Reproduce

I’m working on a C++ codebase, but it happens in other contexts as well. I’m using claude-4-sonnet, in case it’s related. The longer the chat history for the current chat, the worse UI responsiveness gets.

Operating System

Linux

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.2.4
VSCode Version: 1.99.3
Commit: a8e95743c5268be73767c46944a71f4465d05c90
Date: 2025-07-10T16:59:43.242Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Linux x64 6.8.0-60-generic

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

2

Hi @yotambarnoy and welcome to Cursor Forum.

Thank you for the bug report. Could you please provide more details what specific UI issues your team is facing so they can be checked and fixed.

  • How long a chat would that mean? How many requests per chat?
  • Which Linux version are you using?

There are improvements coming to Linux version that may fix your issue but more details may be necessary to pinpoint the cause.

Could you also post errors from Console?

Help > Developer Tools > Console

3

Thanks for getting back to me.

We’re using either Ubuntu 22.04 or 24.04. In general, we experience a lack of UI responsiveness that appears to get worse as the length of the current chat increases, but I can’t say for sure. In my personal experience, clearing the current chat helps significantly. It gets to the point where linux/gnome keeps reporting that Cursor has stopped responding and offering a force quit. It starts occasionally and eventually the popup comes up every second or so and any input into Cursor becomes impossible.

Now that I know about the Console, I’ll post it once I get into that state again – currently it’s full of historical junk.

4

thanks @yotambarnoy, you can clear the Developer Tools - Console any time to see only new entries.

UI issues were reported before and Cursor Team is working on improvements but I would like to check if your issue is related.

5

cursor1.log.txt (601.5 KB)
Posting my log. It’s not very laggy yet, but it seems to be getting there. Will post more if things get worse.

1 Like
6

cursor2.log.txt (497.2 KB)
Starting to get serious lag. Maximum call stack size exceeded.

7

cursor3.log.txt (151.7 KB)
Version: 1.3.9
VSCode Version: 1.99.3
Commit: 54c27320fab08c9f5dd5873f07fca101f7a3e070
Date: 2025-08-01T20:15:21.999Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Linux x64 6.8.0-60-generic

Current version. Still having issues.

8

cursor4.log.txt (363.8 KB)

Constantly getting prompted to force close Cursor, making work very difficult.

9

Thank you, we are working on performance improvements and will release it soon.

10

Just FYI: we’re about to abandon Cursor as a team/company, so unless soon is very soon, you will lose us as customers.

11

We have made today a pre-release where beta test users confirmed bug fixes and improvements in performance. An update is coming soon for all Default channel users.

12

You can try the 1.4 build by changing Cursor Settings > Beta > Update Access: Early Access

13

Just wanted to report that the issues we’ve been facing seem to have improved dramatically. Great job!

1 Like