# Closing/Killing Cursor IDE does not kill all background processes

**URL:** <https://forum.cursor.com/t/closing-killing-cursor-ide-does-not-kill-all-background-processes/159063>\
**Category:** Bug Reports\
**Tags:** linux, performance\
**Created:** [April 26, 2026, 12:01pm UTC](https://forum.cursor.com/t/closing-killing-cursor-ide-does-not-kill-all-background-processes/159063 "2026-04-26T12:01:05Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [April 26, 2026, 1:10pm UTC](https://forum.cursor.com/t/closing-killing-cursor-ide-does-not-kill-all-background-processes/159063/5 "2026-04-26T13:10:24Z")

</div>

Hey, thanks for the report. This is a known issue. The extension host and related processes sometimes ignore SIGTERM when you close the window, so the tray icon and background processes stay alive and you have to kill them manually. It’s not only on Linux, there are similar reports on macOS and Windows too:

- [Xtension-host processes orphaned after window close/reuse — SIGTERM ignored, requires SIGKILL](https://forum.cursor.com/t/xtension-host-processes-orphaned-after-window-close-reuse-sigterm-ignored-requires-sigkill/155821)
- [Windows 11 CPU runs hot even after shutting down Cursor](https://forum.cursor.com/t/windows-11-cpu-runs-hot-even-after-shutting-down-cursor/156643)

We’ve logged the bug, but I can’t share an ETA for a fix yet.

If you can, please send the output of `ps aux | grep -iE 'cursor|code'` right after closing the IDE while the tray is still there. I want to confirm which processes are still running: extension host, shared process, ripgrep, or something else. That’ll help us pinpoint where the shutdown sequence gets stuck.

---

_[View the full topic](https://forum.cursor.com/t/closing-killing-cursor-ide-does-not-kill-all-background-processes/159063)._