posit-dev / posit-dev/positron

Remote SSH: High virtual memory usage when connected to session

Open
#12,967 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area: remote host investigate support
Dominant language
TypeScript
Stars
4.3k
Forks
184
Avg merge
1d 11h
Merged PRs (30d)
206

Description

System details:

Positron and OS details:

Positron Version: 2026.05.0 (system setup) build 30
Code - OSS Version: 1.109.2
Commit: d2bce05424152f00e9164e2ea655d53d32e6e232
Date: 2026-04-09T08:15:15.721Z
Electron: 39.3.0
Chromium: 142.0.7444.265
Node.js: 22.21.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

Session details:

R 4.5.3

Describe the issue:

I am encountering an issue when using Positron on a remote server via SSH.

Upon establishing a connection, before launching any R or Python processes, I observe multiple processes each consuming approximately 60GB of virtual memory. This behavior consistently leads to crashes when running memory-intensive workloads.

The issue occurs immediately after connecting, without starting any job or script. It appears to be independent of whether I use R or Python.
This suggests the possibility of orphaned sessions being loaded into memory. However, the kernel supervisor does not display any active or problematic sessions.

Troubleshooting steps already attempted:

Fully nuked and reinstalled Positron on both my local machine and the server.
Cleared virtual memory on the server.
Despite these steps, the issue reappears immediately upon reconnecting via SSH.

Steps to reproduce the issue:

  1. Connect to remote server
  2. High virtual memory usage (checked using htop)

Attached htop output:
Image

Expected or desired behavior:

Low memory usage when idle.

Were there any error messages in the UI, Output panel, or Developer Tools console?

No

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue by connecting to the remote server over SSH, then inspect htop and the kernel supervisor before starting an R or Python process. Compare the idle processes and their virtual memory usage after a fresh connection. Done means an idle remote session no longer creates multiple processes with approximately 60GB of virtual memory.

Written by the indexing model from the issue text.

Assessment

Tech stack
electron, python, r
Domain
infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.