We're investigating a breaking change introduced by Google in their latest version of Chrome (version prefix 95).

This error appears to have been resolved in an upcoming development version of Chrome and is not affecting other browsers. We're investigating a way to resolve these performance issues in the current version.

In the meantime, we recommend using an alternative browser if possible and will keep you posted on updates here.

Did this answer your question?