webapp error: ResizeObserver loop limit exceeded

[haraldschilly]

This is a weird one, and I'm not sure if there is even a negative impact, but I'm still reporting it. It could lead to further problems down the road while executing and rendering the webapp. I don't know where that exceptions happens, but it does seem to affect all sorts of file types (i.e. not specific to an editor). In particular, it happens for sagews (most of them, at least what I can see right now), ipynb and mp4 videos (that media viewer)

edit: could be chrome specific

smc_git_rev: d1100d5

Date: 2018-10-08 11:06:14.589934

ResizeObserver loop limit exceeded

<generated>
Error
    at s (https://cocalc.com/static/smc-2dc89e44f1881c034548.cacheme.js?2dc89e44f1881c034548:5:862198)
    at https://cocalc.com/static/smc-2dc89e44f1881c034548.cacheme.js?2dc89e44f1881c034548:5:863959

[williamstein]

Weird/interesting. I wonder if this is indirectly caused by terminals, since I made my first ever explicit use of ResizeObserver there... Maybe I screwed up something.

[williamstein]

According to stack overflow: "You can safely ignore this error. One of the specification authors wrote in a comment to your question but it is not an answer and it is not clear in the comment that the answer is really the most important one in this thread, and the one that made me comfortable to ignore it in our Sentry logs.

'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). – Aleksandar Totic Apr 15 at 3:14'"

@haraldschilly --- is their a client-side filter right now for stuff to NOT report to the backend? E.g., the websocket connect errors, obviously, and this, and probably much more. It's a waste of bandwidth, database space, etc. to keep reporting them.