ResizeObserver loop limit exceeded
See original GitHub issueEver since that we started using react-cool-dimensions
that we’ve been having a lot of logged errors:
ResizeObserver loop limit exceeded
Based on this StackOverflow answer it’s not really something to worry about, however, it can be improved by wrapping the ResizeObserver updates in a requestAnimationFrame
.
Here’s an example of how a similar library (not a hook) solved this.
Do you think we can get such an improvement into react-cool-dimensions
?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:24 (23 by maintainers)
Top Results From Across the Web
ResizeObserver - loop limit exceeded - Stack Overflow
This error means that ResizeObserver was not able to deliver all observations within a single animation frame. It is benign (your site will...
Read more >Error: ResizeObserver loop limit exceeded · Issue #5440
Resizing window triggers Error: ResizeObserver loop limit exceeded . The error is not logged in browser's console, but Sentry captures it.
Read more >Uncaught exception: ResizeObserver loop limit exceeded
This is a legitimate problem, and the runtime error is in the console code. Regardless of what's in the CSV, the console should...
Read more >ResizeObserver loop limit exceeded - Perspective - Ignition
I'm having a performance issue with perspective. The problem happens in a table component. I have two Arrays Object with 36 keys:values each ......
Read more >Every time when I edit something in Tableau online, it ...
"ResizeObserver loop limit exceeded." Anyone knows how to fix this problem?
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
We have logs from the latest browser versions, so I don’t think this only happens on old versions.
In my opinion, yes.
Everyone that uses this library with some logging service (like Sentry) will probably come across this “issue”. And I say “issue” because it’s not really affecting functionality (as far as we know), but we have around 34k events affecting 18k users on this “issue” alone. We could ignore it on our system, but based on the links I posted above, this should be easily fixable.
I understand that without reproducing it, it’s hard to understand if we are actually fixing anything. And I can’t reproduce it myself either, so the best I could do is try to deploy a version with a similar fix to the ones mentioned above, and see if the logs start to go away.
Yes I did, @wellyshen, thanks for catching that 😅
Just updated our internal PR 😊