Potential listener LEAK detected, having 175 listeners already

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Agent is keep freezing and I need to stop and re-run the task again and again.
after check the logs, I see the following errors:

ERR [01b] potential listener LEAK detected, having 175 listeners already. MOST frequent listener (1):: Error
at Guc.create (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:47:12844)
at xgr._event [as onDidChangeContext] (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:49:1650)
at xzd.updateParentChangeListener (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:8134:30437)
at new xzd (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:8134:30061)
at xgr.createScoped (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:8134:28306)
at new o
(vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:291:15065)
at new L0 (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:536:25967)
at S2r._createInstance (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:8194:2025)
at S2r.createInstance (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:8194:1454)
at Object.fn (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:6707:1049)
at S8o (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:276:30033)
at cet (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:276:29787)
at hDt (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:276:31414)
at lRu (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:276:32816)
at vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:276:32276
at uG (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:276:31592)
at oRu (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:276:32269)
at uG (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:276:31603)
at w8o (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:276:29471)
at n (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:276:24657)
at IntersectionObserver.threshold (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:7945:38298) ListenerLeakError: [01b] potential listener LEAK detected, having 175 listeners already. MOST frequent listener (1):

Steps to Reproduce

Any Task.

Operating System

Linux

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.7.54
VSCode Version: 1.99.3
Commit: 5c17eb2968a37f66bc6662f48d6356a100b67be0
Date: 2025-10-21T19:07:38.476Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Linux x64 6.8.0-86-generic

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, thanks for the report. It looks like the listener leak affects version 1.7.54.

To help diagnose, could you please share:

  • What extensions are installed? (Help → Extensions)
  • Does the issue still occur if you start Cursor with the --disable-extensions flag?
  • What type of project/codebase are you working with?

In the meantime, you could try:

  • Restarting Cursor when you notice the freezing
  • Temporarily disabling extensions to see if one of them is causing the leak

We have at least one other similar report on the same version.

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