So I've recenty started to use Compose Desktop (0.4.0build185) and even the template app causes the memory to rise every time the user clicks the button. Actually it seems like every time the UI is recomposed, the memory increases. It has reached over 1.4GB at times. Has anyone else seen this?

Are you sure that this is your application and not another?

@Dario Valdespino If you think you've found a memory leak in Compose-desktop, please file an issue on github with a minimal repro.

@Bogdan I'm pretty sure there's no other 'MainKt' running in my machine. Its weird, and I'm only asking here because I think it's too big of a bug to be real. However I'm not doing anything at all, it's just the template app with a button.

well, there are usually several processes there: 1 IDEA 2 Gradle 3 Kotlin Compiler

I know, but my app shows up as 'MainKt', Idea and such appear as 'java'

You can use

jps -m

to get a more detailed name of all the java processes.

it's too big of a bug to be real

The compose codepath can be very hot, especially if an animation is running or something similar. If there is an edge case with a small leak, it could add up fast. If you have a minimal repro that demonstrates the bug, please file a bug on github.

How did you examine the memory consumption? It is quite normal that the memory increases if you haven’t forced a full garbage collection. The GC does not automatically keep the memory at its minimum if there is no need for that.

Through the system monitor mostly. I made sure to manually trigger the GC while testing it. I thought about GC too at first, but 1.4GB of RAM for a program that only shows a button is too much!

You should check that again with a tool like VisualVM for example. It depends on the garbage collector you use whether it returns memory to the system at all. If you allow it to use that much RAM it will happily use that and you will not see any decrease in the system monitor.

I'll try that, thanks for the tip. It must be something like that, the garbage collector not returning memory to the system. I'll have to look up how to limit the JVM's memory usage.