[Bug] - Memory Leak when using firefox to connect kasm
Existing Resources
- [X] Please search the existing issues for related problems
- [X] Consult the product documentation : Docs
- [X] Consult the FAQ : FAQ
- [X] Consult the Troubleshooting Guide : Guide
- [X] Reviewed existing training videos: Youtube
Describe the bug When accessing Kasm via Firefox, the memory usage of the Kasm tab (as shown in the Firefox Task Manager) continuously increases without limit until Firefox crashes. On some PCs, Firefox crashes when the Kasm tab reaches about 2GB of memory usage, while on others it climbs up to 5GB before either crashing or stabilizing.
To Reproduce Steps to reproduce the behavior:
- Use Firefox to go to 'kasmweb.com'
- Click on 'Cloud Browser'
- Scroll down to 'bbc.com.uk' and play a video
- Go to Firefox Task Manager and see the memory usage of the kasmweb.com Tab
Expected behavior Memory usage should remain stable during normal usage and not cause the browser to crash.
Screenshots If applicable, add screenshots to help explain your problem.
Workspaces Version The issue occurs both on self-hosted installations Version 1.17.0 and on Kasm’s public demo at [kasmweb.com] (https://kasmweb.com/) (under the "Try It Now" section).
Workspaces Installation Method
- kasmweb.com Demo installation
- also Single Server
(Client Browser (please complete the following information):
- OS: Windows 11
- Browser: Firefox
- Version: 137.0.2, 64-bit
Workspace Server Information (please provide the output of the following commands): N/A
Additional context
- This issue does not occur when using Chrome version 135.0.7049.115 (Official Build) (64-bit).
- The issue appears to be specific to Firefox.
- Problem has been observed across multiple PCs with varying hardware.
Thank you for reporting. We will look into it
I see the same behaviour.
Is there any workaround to resolve this issue?
Is there any workaround to resolve this issue?
There are two:
- Don't use KASM
- Don't use Firefox.
Is there any workaround to resolve this issue?
There are two:
- Don't use KASM
- Don't use Firefox.
Are you serious? :)
Quick update, we have a fix in a pull request for this, in testing we found an unrelated bug in multi-monitor. We will be retesting and hoping to get the update in the developer preview image tags this week.
Is there any workaround to resolve this issue?
There are two:
- Don't use KASM
- Don't use Firefox.
Are you serious? :)
Yes, but also extremely facetious. The update by @mmcclaskey above is wonderful news, and is the only thing worth paying attention to here.