Cursor 2.2.36 leaks like a sieve

Support Bug Reports
61

workbench.desktop.main.js:58 ERR [Extension Host] [otel.error] {“stack”:“OTLPExporterError: Bad Request\n\tat IncomingMessage. (/home/skaro/.cursor-server/bin/dc8361355d709f306d5159635a677a571b277bc0/node_modules/@opentelemetry/otlp-exporter-base/build/src/transport/http-transport-utils.js:52:31)\n\tat IncomingMessage.emit (node:events:530:35)\n\tat endReadableNT (node:internal/streams/readable:1698:12)\n\tat process.processTicksAndRejections (node:internal/process/task_queues:82:21)”,“message”:“Bad Request”,“code”:“400”,“name”:“OTLPExporterError”,“data”:“{"error":"Trace spans collection is disabled for NO_STORAGE privacy mode"}”}

I think for me this is the main issue and it seems to never stop.
I have legacy mode, I dont want to export any data whatsoever for privacy reasons.
Not sure this is what is causing the memory leak.

62

Hey @skaro, yeah, this OTEL error loop is very likely causing, or at least contributing to, a memory leak. It’s a known bug. Starting in version 2.3.35, telemetry was added that tries to send trace data, but when the server rejects it, in your case because of NO_STORAGE privacy mode, the errors build up in memory instead of being handled properly. Over time, that can lead to an OOM.

A detailed breakdown is posted here: 2.3.35 > Repeated OOM crashes

Can you share what Cursor version you’re currently on?

63

It’s a js heap buffer leak, these instructions won’t help