v4.99.3 Memory Leak

[djarbz]

Is there an existing issue for this?

• I have searched the existing issues

OS/Web Information

• Web Browser: Edge
• Local OS: Windows 11
• Remote OS: Fedora 41
• Remote Architecture: amd64
• code-server --version: 4.99.3

Steps to Reproduce

1. Open Code server in MS Edge
2. Wait...
3. Watch Memory usage spike rapidly in the Edge Process Explorer as the interface becomes unresponsive.
4. Refresh Code Server page, memory does not release but I can interact for a few minutes before it becomes unresponsive again.

Expected

Memory should not balloon drastically and the interface should remain quite responsive.

Actual

Memory and CPU usage quickly becomes drastic and the interface locks up until an out of memory error occurs.

Logs

Might need some guidance in collecting the logs from a Coder Workspaces session.

Screenshot/Video

No response

Does this bug reproduce in native VS Code?

I did not test native VS Code

Does this bug reproduce in GitHub Codespaces?

I did not test GitHub Codespaces

Are you accessing code-server over a secure context?

• I am using a secure context.

Notes

code-server: v4.99.3
Code: 1.99.3
Commit: c36b2d3
Date: 2025-04-16T22:22:02.429Z (4 days ago)
Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/135.0.0.0 Safari/537.36 Edg/135.0.0.0

I am using Coder Workspaces for my backend.
I am not seeing an issue in Google Chrome or Firefox.

[nowarzz]

I am experiencing the same in google chrome, but not in firefox. I haven't tried using edge

[code-asher]

Definitely curious to see if y'all can reproduce in Codespaces. I am not sure what we could have patched to create a memory leak, not impossible but it might be an upstream bug.

Although, I am not sure but, I think in Codespaces when you refresh it recreates the server, so it might not reproduce so easily there.

[benz0li]

@djarbz Can you reproduce at https://demo.jupyter.b-data.ch? All available images there serve code-server v4.99.3.

I cannot reproduce when using Microsoft Edge v135.0.3179.85 (Official build) (64-bit).

[djarbz]

Using Edge v135.0.3179.85 (Official build) (64-bit), it sat at 300k for a bit, but then skyrocketed up just sitting there without me actually doing anything. I'm assuming this means that it is an upstream issue?

Google Chrome v135.0.7049.96 (Official Build) (64-bit) remains stable for me, again, not doing anything but letting is sit.

Firefox v137.0.2 (64-bit) behaved much the same as Google Chrome.

[benz0li]

I'm assuming this means that it is an upstream issue?

Seems more like a browser issue.

[benz0li]

I have these images running code-server all day long without any issues.

[benz0li]

@djarbz Any errors in the browser console? Other things that may cause problems:

1. Browser extensions
2. Private Mode
3. Firewall

[djarbz]

Interesting, Private Mode did not crash.
I disabled the BitWarden extension and normal mode has not crashed yet either...

I re-enabled BitWarden and the memory usage started creeping back up, even in a "locked" state.
Does anyone else have BitWarden that they can verify my findings?
I do have BitWarden on my Chrome and Firefox browsers as well.

What is the next step in troubleshooting to see if it is in fact a BW or CS issue?