search

plotly / plotly.js

Open-source JavaScript charting library behind Plotly and Dash
https://plotly.com/javascript/
MIT License
17.08k stars 1.87k forks source link

`Chrome 128` seems to have problem rendering WebGL traces including `parcoords`, `mesh3d`, `surface` #7130

Closed archmoj closed 2 months ago

archmoj commented 2 months ago

As discovered in #7126 this might be either a regression in Chrome 128 or a bug in plotly.js & stackgl dependencies. cc: @birkskyum

Error message: 

TypeError: Failed to execute 'uniformMatrix4fv' on 'WebGLRenderingContext': The provided float value is non-finite.
archmoj commented 2 months ago

Keeping an eye on https://issues.chromium.org/issues?q=componentid:1456284.

archmoj commented 2 months ago

I could confirm that e.g. this parcoords graph is not rendering on Chrome 128 as well as Edge 128.

archmoj commented 2 months ago

Other applications also encountered this: https://community.esri.com/t5/arcgis-online-questions/map-error-in-new-chrome-update-128-0-6613-85/td-p/1525829

archmoj commented 2 months ago

FYI chromium.org considered this regression and labeled it as P1. See https://issues.chromium.org/issues/361823993.

archmoj commented 2 months ago

The regression is now fixed by Chromium 128.0.6613.113 https://chromium.googlesource.com/chromium/src/+/refs/tags/128.0.6613.113 Please consider updating your browser if you encountered this bug. Closing.

percybolmer commented 2 months ago

Had this error occur, patch worked like a charm! Thanks for updating regarding this here.