I am using Compose MP on iOS extensively, and when...
# compose-ios
t
I am using Compose MP on iOS extensively, and when debugging, I see a huge spike in CPU and memory when running in a simulator. Has anybody seen this? See thread...
visual:
g
I just fired up my project and didn't see any, no. Do you have any kind of logging/debugging attached?
t
No logging that I recall putting in there, no. I am not even sure those GC threads are Kotlin related, though I am assuming since the whole view is compose mp. The testers have not seen anything, but when i see it myself I worry. Though it appears to be a bit less with the latest 1.6.0-rc01 CMP.
g
In my experience the simulator just acts up sometimes, I've had mine run doggedly slow on a native swift project and then the next day it was fine with no changes. I'd try to validate any impact on an actual device and just keep an eye on it personally
t
Yeah, I will def. do that. Once I get my shared code built again for watchOS (I have to rebuild my shared code differently for watchOS, since CMP is not supported there).
g
I've always thought it was maybe the native debugger in the simulator deciding it wanted to do something, or even the iOS indexer service doing stuff