Hey, this looks very similar to a known issue where the bundled V8 engine crashes on remote Linux hosts whose CPU doesn’t support Intel PKU Memory Protection Keys. There’s a related report here: Remote SSH: Segmentation fault (SEGV_PKUERR) on CPUs without PKU support.
To confirm, can you run this on the remote machine or inside the Docker container:
grep pku /proc/cpuinfo
If it returns empty, that’s the cause.
Workaround: Add this line to the cursor-server startup script on the remote before the last line ~/.cursor-server/bin/linux-x64/<commit>/bin/cursor-server:
export NODE_OPTIONS="--no-node-snapshot --jitless"
Note: --jitless disables V8 JIT, so things will be a bit slower, but tsserver should stop crashing. Also keep in mind this gets overwritten on every Cursor update, so you’ll need to re-apply it.
Could you also check Output panel > TypeScript for the actual crash signal or error? That would help confirm the exact cause.
The team is aware of this issue. No timeline on a fix yet, but your report helps with prioritization, especially since you’re hitting it through Docker containers, which adds another data point.
Let me know how it goes.