Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
archmoj opened this issue Aug 22, 2024 · 6 comments
Closed

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

archmoj opened this issue Aug 22, 2024 · 6 comments
Assignees
@archmoj
Labels
bug something broken P2 considered for next cycle

Comments

@archmoj
Copy link
Contributor

archmoj commented Aug 22, 2024 •
edited
Loading

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.
@gvwilson gvwilson added bug something broken P2 considered for next cycle labels Aug 26, 2024
@archmoj
Copy link
Contributor Author

archmoj commented Aug 26, 2024

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

@archmoj
Copy link
Contributor Author

archmoj commented Aug 26, 2024

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

@archmoj archmoj changed the title Chrome 128 seems to have problem rendering some of our WebGL traces e.g. parcoords and surface Chrome 128 seems to have problem rendering the parcoords WebGL trace Aug 26, 2024
@archmoj archmoj changed the title Chrome 128 seems to have problem rendering the parcoords WebGL trace Chrome 128 seems to have problem rendering WebGL traces including parcoords, mesh3d, surface Aug 26, 2024
@archmoj archmoj mentioned this issue Aug 26, 2024
Closed
@alexcjohnson alexcjohnson mentioned this issue Aug 27, 2024
Closed
@archmoj
Copy link
Contributor Author

archmoj commented Aug 27, 2024

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

@c-bata c-bata mentioned this issue Aug 28, 2024
Merged
1 task
@archmoj
Copy link
Contributor Author

archmoj commented Aug 28, 2024

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

@archmoj
Copy link
Contributor Author

archmoj commented Aug 28, 2024

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.

@archmoj archmoj closed this as completed Aug 28, 2024
@archmoj archmoj mentioned this issue Aug 29, 2024
Merged
@percybolmer
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@archmoj archmoj

Labels
bug something broken P2 considered for next cycle
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix rendering of WebGL traces on latest Chrome-128 and Edge-128 browsers plotly/plotly.js
3 participants
@gvwilson @percybolmer @archmoj