CMD+Click "Finding Reference" is slow with Python

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When using “Go To References” feature, SHIFT + F12 or CMD+Left click, it is incredibly slow.

“Finding references” shows in the bottom bar with a spinner, it takes a long time, 10+ seconds.

With brand-new Cursor install and python-ms installed

Steps to Reproduce

Install Cursor, open a python project, click a python file, install python-ms as prompted by Cursor, do CMD+Left Click on a method or object.

NB: quitting cursor and restarting it does not fix this issue.

Expected Behavior

It should be MUCH faster. This is NOT a usable IDE.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.5.11 (Universal)
VSCode Version: 1.99.3
Commit: 2f2737de9aa376933d975ae30290447c910fdf40
Date: 2025-09-05T03:48:32.332Z (3 days ago)
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.6.0

Does this stop you from using Cursor

Yes - Cursor is unusable

1 Like

Having the same issue

@ravirahman is this a known issue or can you offer any assistance here? its taking very very long for me and making Cursor unusable for me and my team

Hi @Jocelyn and @Ryan_St_Pierre, could you try adding paths to cursorpyright.analysis.exclude? This will limit the # of files that are getting analyzed, which should help improve performance.

Cloning the repo in a different directory and starting from that fixed it for me, but I suspect there is an underlying issue that it just side-step. Other team mates are still reporting the issue.

@ravirahman added to exclude all files and i added [tool.pyright]
typeCheckingMode = “off”

After doing both and restart still a problem . Takes minutes spinning on “Finding References” . unusable at this point for me :frowning:

This seems like a recent issue. did something change? I’m pretty confused bc non of my IDE’s have this problem. Including VSCode on the same repo. Using pycharm now and also fine

Please advise

If it’s stuck on Finding References, that sounds like the language server has crashed. Could you take a look at the “Cursor - Pyright” and “basedpyright” output consoles? It might also help to give more RAM to the language server; we default to ~1/2 of the available RAM, but for large projects, sometimes more can be helpful. You can increase it via the setting cursorpyright.nodeMaxOldSpaceSize.

Is there a good way to figure out where cursorpyright is spending most of its time finding references? Unable to find this info in the output consoles.

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