Hey, this is a known issue.
The "Trace spans collection is not enabled for this user" error usually means Privacy Mode is enabled, and the server rejects telemetry because of that. The spans keep retrying and building up instead of being dropped.
Workaround: try turning off Privacy Mode in Cursor Settings > General > Privacy Mode. That lets the server accept spans instead of rejecting them, which stops the memory buildup.
If you need Privacy Mode on (for example, for proprietary code), the only option right now is to rotate chats often and watch memory in Ctrl+Shift+P > Developer: Open Process Explorer.
Related threads with more context:
- Renderer OOM crash: OTEL exporter leaks memory when trace spans rejected (400)
- Cursor crashes repeatedly with out-of-memory (OOM) errors after the latest update, especially during large prompts or long-running plans
The team is aware of this. No ETA yet, but your report helps with prioritization. Let me know if turning off Privacy Mode helps.