ResizeObserver loop limit exceeded

[lynnic26]

Kibana version: 6.1.2

Browser version: chrome 68 Browser OS version: mac Original install method (e.g. download page, yum, from source, etc.): from source Describe the bug:

I came across this error when clicking on a video fullscreen button in kibana This only happens on Chrome browser , how can I get rid of it or if there is a workaround for this?

here is an image about this

[cjcenizal]

CC @elastic/kibana-visualizations I'm pinging you because it looks like this ResizeObserver is used by our ResizeChecker, which has been mostly edited by @timroes.

[timroes]

Could you please elaborate where the video fullscreen button came from, that triggered that?

[lynnic26]

Could you please elaborate where the video fullscreen button came from, that triggered that?

@timroes Yes, I add a video player list in the visualization page(the video list data are from elasticsearch), and each has a fullscreen button when click the fullscreen button, it will redirect to the error page

[salihkardan]

any updates on this ?

[timroes]

@lynnic26 Could you please check if you are using any third party plugins, since Kibana doesn't have such a thing as a video player fullscreen in it? Could you please also provide screenshots of the page/state before that error happened?

[salihkardan]

Actually I commented on this issue, since I also have same problem with my pluing and I am not using any third party plugins. I am not sure but error may be related to EUI framework. By the way, I don't get this error on safari.

[timroes]

Closing this issue due to inactivity.

We are trying to keep our issues to a manageable amount, why we are trying to close issues we cannot reproduce or gather required information for some time. Please feel still free to provide the requested information in case the issue still persists on an up-to-date Kibana version. We can then reopen this issue again.

[Austio]

@timroes I am still seeing this on my end (6.6.1). I am able to access just fine in firefox or safari. This error appears to be completely benign so should be something that kibana gracefully handles instead of crashing.

https://stackoverflow.com/questions/49384120/resizeobserver-loop-limit-exceeded

[lukeelmers]

Reopening, as this was reported again recently in #35862

[Austio]

@lukeelmers please let me know if you need anything on this.

[jakalt]

I also face this error on Kibana 6.4.4 and 6.4.1. using a custom visualization plugin. The error from ResizeObserver and could safely be ignored by kibana instead of crashing, according to this post: https://stackoverflow.com/questions/49384120/resizeobserver-loop-limit-exceeded

This error means that ResizeObserver was not able to deliver all observations within a single animation frame. It is benign (your site will not break)

[joshdover]

While working on adding back our global window.onerror handler, I noticed this error starting to happen in some functional tests. Unfortunately the error does not give us a stack trace.

I tried disabling all of the ResizeObservers in the Kibana repo and the issue persisted. It must be happening in a dependency, most likely EUI. I'll try investigating this deeper and see if I can't hunt this down in EUI.

[Timothee]

FWIW, I came across this issue by searching for this error. I also came across this StackOverflow question which seems to say these errors can be safely ignored.

Hopefully that helps. 🙂

[joshdover]

That may be the most practical way forward to add back the window.onerror handler (#45531), but there are probably some performance issues caused by the code triggering this error.

[dmccrevan]

Is there any update on this? I am observing this same issue only on Firefox.

I have kibana has an embedded iframe on my web application. I reproduce this when the kibana is in the discover tab, and the iframe goes from inactive back to active.

I don't see this on chrome.

[a1exus]

confirmed same issue w/ chrome81/macos(mojave)

[markov00]

@dmccrevan @a1exus what Kibana version are your running? could you share the URL and the error stack reported?

[macgaver]

Same issue on kibana 7.2.0 with my firefox v75.0 (ok with chrome).

Version: 7.2.0 Build: 24337 Error: ResizeObserver loop completed with undelivered notifications. (:0) window.onerror@https://10.128.8.101/kibana/bundles/commons.bundle.js:3:1616339

Error: ResizeObserver loop completed with undelivered notifications. (:0) (https://10.128.8.101/kibana/bundles/commons.bundle.js:3) Version: 7.2.0 Build: 24337 Error: Error: ResizeObserver loop completed with undelivered notifications. (:0) (https://10.128.8.101/kibana/bundles/commons.bundle.js:3) window.onerror@https://10.128.8.101/kibana/bundles/commons.bundle.js:3:1616339

[tylersmalley]

We're seeing this error in the APM data collected from running the Functional Tests in CI about 70,000 times a day.

url.domain	localhost
url.fragment	/edit/81eab320-3a57-11eb-bf94-a14630a76b81?_g=(filters:!(),refreshInterval:(pause:!t,value:0),time:(from:'2015-09-19T06:31:44.000Z',to:'2015-09-23T18:31:44.000Z'))
url.full	http://localhost:6111/app/lens#/edit/81eab320-3a57-11eb-bf94-a14630a76b81?_g=(filters:!(),refreshInterval:(pause:!t,value:0),time:(from:%272015-09-19T06:31:44.000Z%27,to:%272015-09-23T18:31:44.000Z%27))
url.original	http://localhost:6111/app/lens#/edit/81eab320-3a57-11eb-bf94-a14630a76b81?_g=(filters:!(),refreshInterval:(pause:!t,value:0),time:(from:'2015-09-19T06:31:44.000Z',to:'2015-09-23T18:31:44.000Z'))
url.path	/app/lens
url.port	6111
url.scheme	http

[flash1293]

I read a bunch of related issues and I'm not sure this is not something we can easily fix - resize observers are throwing an error bubbling up to window.onerror if there are unhandled resize events which couldn't be handled in a single animation frame.

There's no way to 100% prevent that as it can happen anytime depending on the available CPU/memory resources on the computer running Kibana.

As the code crashing all of Kibana due to this error got removed, I would suggest closing this issue (as the main point got addressed and the code changed significantly since this issue was opened, so the discussion in here is not up to date anymore). We try to improve performance of Lens as a whole, but I don't think it makes sense focusing on this error.

@joshdover what do you think? Related issue https://github.com/elastic/kibana/issues/45531

[joshdover]

resize observers are throwing an error bubbling up to window.onerror if there are unhandled resize events which couldn't be handled in a single animation frame.

I believe this tends to happen when there is some sort of loop involved. One resize event handler triggers another resize, triggering another event, and so on. That feels like a bug, but I don't have a hard example to point to. Without a stacktrace on these errors it's quite hard to determine where these are even originating from. I wonder if it's possible for us to find the e.target to determine which DOM element(s) this is happening on.

I think it would be worth doing that analysis before we close this issue. We should be pretty sure this error is actually safe to ignore and isn't causing issues on lower-end hardware before we ignore it. It's possible that the impact is low, but noisy. If that's the case, I think we should leave this open for visibility and see if we can't improve the error reporting so it's more specific to an area(s) of the DOM where this is happening.

[flash1293]

@tylersmalley We recently fixed a bug related to "twitching" of the rendered charts in Lens - did this resolve the issue or is the number of errors still that high?

[tylersmalley]

Hey @flash1293, still seeing these errors. You can view them here: https://e88521bb9a6c4b5aa6ac7d81d3dcefd4.us-east-1.aws.found.io:9243/goto/e3bd676e4ddfb9a36ad0288b5e92c556

While there are some in Lens, they are happening in a lot of other parts of the application as well.

[elasticmachine]

Pinging @elastic/kibana-design (Team:Kibana-Design)

[lizozom]

Looking at APM data this error still exists on latest prod versions. Seems like it's the most common error we have.

This is data from our qa monitoring cluster and it seems like these errors are coming mostly from various apps)