workspaces-issues icon indicating copy to clipboard operation
workspaces-issues copied to clipboard

[Bug] - Memory Leak when using firefox to connect kasm

Open mimbiesdev opened this issue 8 months ago • 7 comments

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:

  1. Use Firefox to go to 'kasmweb.com'
  2. Click on 'Cloud Browser'
  3. Scroll down to 'bbc.com.uk' and play a video
  4. 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.

mimbiesdev avatar Apr 27 '25 10:04 mimbiesdev

Thank you for reporting. We will look into it

j-travis avatar Apr 28 '25 12:04 j-travis

I see the same behaviour.

garethhumphriesgkc avatar Apr 29 '25 21:04 garethhumphriesgkc

Is there any workaround to resolve this issue?

mimbiesdev avatar Jul 02 '25 14:07 mimbiesdev

Is there any workaround to resolve this issue?

There are two:

  1. Don't use KASM
  2. Don't use Firefox.

garethhumphriesgkc avatar Jul 02 '25 20:07 garethhumphriesgkc

Is there any workaround to resolve this issue?

There are two:

  1. Don't use KASM
  2. Don't use Firefox.

Are you serious? :)

mimbiesdev avatar Jul 07 '25 12:07 mimbiesdev

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.

mmcclaskey avatar Jul 07 '25 13:07 mmcclaskey

Is there any workaround to resolve this issue?

There are two:

  1. Don't use KASM
  2. 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.

garethhumphriesgkc avatar Jul 07 '25 21:07 garethhumphriesgkc