Hi guys I have another issue with the r*ecompositi...

# compose

[Tung97 Hl]

Hi guys I have another issue with the r*ecomposition again.* 😂 The detail in the thread. Please take a look.

[Tung97 Hl]

Here is the old conversation https://kotlinlang.slack.com/archives/CJLTWPH7S/p1673953852002799

[Tung97 Hl]

Now my Numpad is inside InputAmountScreen. I think it is not a trouble.

[Tung97 Hl]

I called InputAmountScreen inside HomeScreen

[Tung97 Hl]

Here is my AppBottomBar

[Tung97 Hl]

My problem is: I have no idea why now the numpad and the input amount screen is recomposed whenever I press any button in numpad

[Tung97 Hl]

Please help 🥲

[Ben Trengrove [G]]

First off, I wouldn't stress about this unless it's causing you some sort of jank

[Ben Trengrove [G]]

But is it just because when you push a button, inputText is updated which causes a recompostion?

[Tung97 Hl]

I don’t know why. Whenever I press the button, the view gets recomposed and increases memory (and it can not be free until I leave this screen). So no jank here, but the memory issue makes me worry.

[Tung97 Hl]

Then I think maybe the unnecessary recomposition here is the cause of memory issue.

[Ben Trengrove [G]]

It doesn't look unnecessary to me

[Ben Trengrove [G]]

Your state is changing and so it recomposes

[Ben Trengrove [G]]

That's just working as normal

[Tung97 Hl]

So what about the memory increase? Do you have any idea about the root cause?

[Tung97 Hl]

Because my targeted device is very weak (only 1gb ram) so if memory can not be free I will be triggered haha

[Ben Trengrove [G]]

Is it that garbage collection just hasn't run yet? Does it go down when you force flush it?

[Tung97 Hl]

yes.

[Ben Trengrove [G]]

That means it is all working correctly

[Tung97 Hl]

Thank you K