[linear-progress] indeterminate animation fails under high CPU load
See original GitHub issueBug report
MDC linear-progress’s indeterminate state’s animation skips frames under large CPU loads.
Steps to reproduce
- Place an indeterminate linear-progress on the page
- Run
while (true) {}
in the console
Actual behavior
The animation pulsates
Expected behavior
The indeterminate animation should be playing
Screenshots
Your Environment:
Software | Version(s) |
---|---|
MDC Web | Canary |
Browser | Chrome 80 |
Operating System | Mac OS 10.15.3 |
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (6 by maintainers)
Top Results From Across the Web
MUI V5: Loading Spinner / Animation - YouTube
In this video we talk about the Progress & Loading states you can import from Material UI V5. There are 2 main components,...
Read more >How to reset Material UI LinearProgress after completion?
I was looking for a way to disable the animation of the reset from 100 to 0 on the LinearProgress as well and...
Read more >Animation QML application make large load of CPU core I.MX6
I compile Qt5.3.1 from source with support OpenGL and when I run my application I have very large use cores of I.MX6 instead...
Read more >Circular, Linear progress React components - Material UI - MUI
High CPU load. Under heavy load, you might lose the stroke dash animation or see random CircularProgress ring widths.
Read more >Build a React Native progress bar - LogRocket Blog
How do you animate a progress bar in React Native? · When the value of count changes, invoke the load method to run...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Correct, following the bug it looks like it was reverted from the stable track because it caused a regression. Here’s the new bug to follow https://bugs.chromium.org/p/chromium/issues/detail?id=389359
But if it still happens with their version of the linear progress, doesn’t that mean Chrome still has a bug?