Ubuntu: Zombie mount_Cursor

Describe the Bug

As it starts and stops or crashes through the day it accumulates more and more

Checking for remaining processes and zombies…
Handling zombie processes…
Warning: Some processes for cursor may still be running.
david 29849 0.0 0.0 15348 8464 pts/2 Ss+ Jul21 0:00 /usr/bin/bash --init-file /tmp/.mount_CursorquU3k8/usr/share/cursor/resources/app/out/vs/workbench/contrib/terminal/common/scripts/shellIntegration-bash.sh
david 199955 0.0 0.0 15492 9304 pts/6 Ss+ 14:52 0:00 /usr/bin/bash --init-file /tmp/.mount_CursorquU3k8/usr/share/cursor/resources/app/out/vs/workbench/contrib/terminal/common/scripts/shellIntegration-bash.sh
david 200320 0.0 0.0 15492 9044 pts/7 Ss+ 14:53 0:00 /usr/bin/bash --init-file /tmp/.mount_CursorquU3k8/usr/share/cursor/resources/app/out/vs/workbench/contrib/terminal/common/scripts/shellIntegration-bash.sh
david 200604 0.0 0.0 15492 8708 pts/8 Ss+ 14:53 0:00 /usr/bin/bash --init-file /tmp/.mount_CursorquU3k8/usr/share/cursor/resources/app/out/vs/workbench/contrib/terminal/common/scripts/shellIntegration-bash.sh

Steps to Reproduce

Use Cursor on Ubuntu:
david@Godzilla:~/Applications$ ./Cursor-1.2.4-x86_64.AppImage

Expected Behavior

not leave zombies, crash less often, stop going to sleep

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.14.0-24-generic

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Hi,

As a ubuntu server user, but also having used RHEL, rocky linux, Alma Linux, Fedora, it is important to hopefully give more insights since any linux user, regardless of the distro, has to some extent the same problems you face.

Google electron app, or any chromium based browser, has an insane amount of telemetry embedded into it. Let’s make it simple:

  • all electron/chromium app share the same ipc crashpad handler by default. Flathub is a mockery of sandboxing and all these apps share telemtry IDs about a lot of usage data. It is a huge attack vector that an attacker can exploit, then spillover flathub through many gnome app (you didn’t knew they had GnomeControleCenter, Dbus access, Keyring etc by default on flathub so you think you are sandboxing app leaving a highway to your core system wide open as to escalate to root access ?)

  • all electron has a shared cookie jar if you do not firejail and/or apparmor/selinux it. Even then it will sandbox some processes of cursorAI, while others are unsandboxed. Look for --zygote (sanboxed), --no-zygote (unsandboxed). CursorAI’s privacy statement by no mean addresses this issue but it is important to assess VScode does as well.

  • auto-updaters will happily phone home insane amounts of telemetry, even if you deactivate it, it still runs without you knowing. Here you have an electron leftover of cursors’ built-in terminal running again and again. And until you reboot, it will continue because electron has this behavior of leaky leftover processes running even if you stop cursor.

It can literally read memory, leaks everything, and any gnome user is a target of massive telemetry

What you see is an unfortunate proof of how bloated, persistent, and poorly designed electron is. My advice is to use only cursor as electron app, firejail it, and keep in mind any electron based app unfortunately behaves exactly the same way… The more you have on your system, the more your attack surface and telemetry collection surface becomes.

I do hope it brings some help and hopefully some clarity about your problem.

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