Replies: 2 comments 7 replies
-
Hi @nikitaame, thanks for providing some code. That definitely helps us look into what you are seeing. However, before even running the project myself, I want to mention that in the screenshot you posted there is a mention of ![]() And that function is only compiled in It's what provides the purple runtime warnings for when So, are you sure you are experiencing performance/CPU problems when running the app for release? This may only be an issue for DEBUG builds. |
Beta Was this translation helpful? Give feedback.
-
Hi @mbrandonw, thanks for taking a look! You are 100% right, there are no issues when running the app for release. Thank you for figuring that out! Unfortunately, it takes ~15 seconds to navigate to the page in the real project. It is part of a developer config modal constantly used in debug mode. Hence the mention of "feature flag" in the sample. I introduced TCA in this dev config modal as a showcase of TCA for our team and would love to polish this if possible. Do you have any suggestions or workarounds? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hey there! I'm trying to debug an issue where I see 100% CPU utilization when opening up a new page that has a list of toggles. I wonder if I am doing something wrong with how I've set things up. The app becomes unresponsive for a noticeably significant amount of time before opening up the page. I've made a sample project that reproduces this issue.
Here's a a snapshot of what is causing the spike in CPU usage:

Screen recording of delay to open page:
RPReplay_Final1717390534.MP4
I had tried removing this line:
from the
ForEach
of theFeatureFlagsView
and its "faster" but then there are hitches in the scrolling while showing the rows for the first time.Beta Was this translation helpful? Give feedback.
All reactions