-
Notifications
You must be signed in to change notification settings - Fork 206
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extremely high CPU usage causing phone to overheat #64
Comments
"Use one [Shimmer] to wrap a list of [Widget]s instead of a list of many [Shimmer]s" Make sure you are not having little shimmers animating themselves instead you need to have parent shimmer, applying animation over multiple containers/placeholders |
Even a single one was causing it - is there a busy wait underneath? A simple animation like this shouldn't cause the overheating. If there is, maybe even a tiny |
Hi everyone! Any updates? |
Interesting, I found similar spike in CPU usage. Were you able to figure out the root cause? I've incorporated @dmitry-grin's feedback but is there anything else we can do to reduce the CPU usage? |
Same here ... |
Do any of you experience this overheating on Android? |
Same here ... |
Same here with |
this is very bad! |
Came across this issue after our users have reported our app is draining battery life and phone getting hot, only on iOS? Similar to @joaopmarquesini Is there away round this or it is due to using multiple shimmers on the one view? |
@b099l3 from what I tried, even if I used a single shimmer but had it constantly on screen (I was using it on animations for a gaming app) the phone would overheat. |
Slightly unrelated but also good to know for others. We also use Intercom in our app and this issue also mentioned high CPU load. BEFOREAFTER |
On my side, I have set the |
Same here on Android, any updates? |
It seems that shimmering causes a ~40-60% CPU usage when running:
It's so severe that my phone overheats.
If I give it a stopping condition (i.e.
loop: 2
), it's reduced considerably:The text was updated successfully, but these errors were encountered: