Compose on iOS resulting huge memory and CPU consumption resulting in ios app crashing, phone warming and freezing issues

[sureshmaidaragi1919]

Describe the problem

In our project, we are seeing two blocker issues, High CPU and Memory consumption on iOS app due to which we have halted the project development until it is resolved. Videos attached here is from our code base, and code base attached for sample demo to reproduce the issue.

Memory consumption issue

We are loading simple Bottomsheet dialog around 10 to 15 times on screen, on each instance it results in 3MB increase and 3MB is not releasing at all even if we come back from the screen

CPU consumption issue:

When a particular job is done by app, immediately CPU should return to 0-1%, which is not happening. in our usecase CPU utlisiation going up to 180% and returning to ~104% and staying in ~104% for around 1min later coming back to 0-1% if app is idle.

• What specific issue did you encounter? high CPU usage and memory leaks
• Have you noticed any patterns or specific circumstances under which the problem occurs? Memory issue: Yes, whenever new screens load memory being added which is not releases when user comes out from that screens. If we close and open 1screen around 15 times there is an increasing memory graph being drawn which is resulting in huge memory consumption, and grows to extent and system crash's the app in case of iOS. CPU issue : Utilise CPU is not releasing up to 30 sec to 1min, resulting in a phone heating issue.

Affected platforms Select one of the platforms below:

• iOS

If the problem is Android-only, report it in the Jetpack Compose tracker

Versions

• Kotlin version: 2.0.0
• Compose Multiplatform version: 1.6.10
• OS version(s) (required for Desktop and iOS issues): All version
• OS architecture (x86 or arm64): Both

Sample code Sample project code link

Reproduction steps Please provide a detailed step-by-step guide on how to reproduce the issue you are experiencing.

Video video link

Profiling data Please provide any relevant profiling data that might be helpful. This could include information like FPS, memory usage, CPU time, or any other data that could provide insight into the performance issue.

Additional information

[terrakok]

Hi. Thank you for the report. We will investigate it soon and will ask you more information if it is required

[elijah-semyonov]

@sureshmaidaragi1919

turning to ~104% and staying in ~104% for around 1min

Can you make a screenshot of all the active threads when this happens? I can't reproduce it.

[sureshmaidaragi1919]

here it is @elijah-semyonov https://drive.google.com/file/d/1-pEe6-UZcy6NGJLgrbNgNb7LdEZCIS3B/view?usp=sharing

[sureshmaidaragi1919]

High CPU was due to Xcode Edit config on debug build, @elijah-semyonov thanks for the suggestion 🙌 🥳 .

Solution: uncheck the below options Main Thread Checker Thread Performance Checker

[terrakok]

Apple root issue: https://discussions.apple.com/thread/255578878?sortBy=best

[sureshmaidaragi1919]

There is memory consumption issue that still persists on compose 1.6.10, when I navigate between two simple screens, it does not completely drop the retained memory when I move back from the screen.

Is there any workaround for this?

[terrakok]

You are supposed

• To file a new issue
• To attach a small reproducer
• To attach your logs

[okushnikov]

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.