4 years ago, a JetBrains article explained how a migration from (basically) Chromium + React to Kotlin Multiplatform reduced the memory consumption.
- Before the migration: “Even when idle, JetBrains Toolbox would use at least 200 MiB of RAM“.
- After the migration: “that situation has improved significantly” … “Compose for Desktop is now much less resource intensive” … “we managed to greatly reduce the RAM used by the app“.
Unfortunately, the Toolbox currently uses at least twice (usually x3) as much memory as it did when it was based on Chromium. Things are even worse as it also starts the new jetbrainsd daemon.
If you think it’s time for JetBrains to revamp and optimize this great tool, I recommend voting in favor of TBX-13108. That’s the best way to bring this issue to JetBrains’ attention.
One last thing: please vote for the ticket itself (the thump-up icon on the top-right corner). Upvotes on comments don’t actually make a difference, because it’s the number of upvotes on the ticket that really counts.