souporserious/react-measure

"ResizeObserver loop limit exceeded" since Chrome update 64

Closed this issue · 11 comments

onchainguy-btc commented

I'm seeing this error message in my console since Chrome update 64. Doesn't seem to have any effect on my UI. Is anybody else having the same issue?

AnthonyKob commented

Exactly the same issue with Chrome 64 or 65

KowalskiP commented

Yes, same issue with 65 version

souporserious commented

Interesting 🤔, I haven't seen this myself yet, I'll have to test it out. It sounds like it might be the polyfill we are using. @que-etc any ideas here?

ryanwisniewski commented

We're getting this exception multiple times daily. Any update?

jessb321 commented

We are having this issue as well over at EDCD/coriolis#208. Happens any time the window resizes.

  • 😕2
michael-ecb commented

For me this error do not appear in chrome console but in "Javascript errors notifier" (chrome extension)
any update ?

  • 👍16
  • 😕4
JabbyPanda commented

Some discussion on ResizeObserver loop limit exceeded WICG/resize-observer#38

felixlinker commented

To enhance on what @willyb321 said - I work on the same repository: I just updated the dependency to ^2.0.0. The error only appears if setState is called in the onResize callback. It doesn't help if we check for values being changed, e.g. do something like @souporserious proposed in #56.

joaovieira commented

Any updates on this? Could this help: airbnb/visx#335?

  • 👍8
yoadsn commented

Followed the same path linked to by @joaovieira - tested locally - this seems to resolve the problem.
@souporserious would you consider merging this? (Basically, monkey copy-paste there)

setState anyway was called sync on the measure callback being not a react callback. When the measured element relies on the measured size to set its own size (well, sometimes you need to do that) this error occurs. i.e setState -> sync render -> size change -> sync observe callback -> setState -> inf. loop detected.

The ResizeObserver loop limit exceeded error would not appear in chrome console - rather you should listen on window for errors (or as one of the above posts mentioned - use an extension).

Do something like this in the console to see if you are affected:

window.addEventListener('error', function(e) { console.log('ooops inf loop'); });

Many auto error-tracking scripts/extensions listen to window errors and this is why this shows up and bothers us develoepers.

hth

  • 🎉10