Label rendering issue in new Chrome versions

[jluethi]

We've recently started to notice the new label rendering in Vizarr fails with errors like:

Uncaught (in promise) Error: Error during validation: Two textures of different types use the same sampler location.
webgl-render-pipeline.js:243 

It leads to the label not loading at all.

This occurs in Chrome (tested in Chrome 138.0.7204.184 & Chrome 141.0.7353.0), but does not occur in Safari (Version 18.5 (20621.2.5.11.8)).

It seems to be related to the specific rendering approach:
Early drafts of label rendering that worked slightly differently still work across browsers for us: https://deploy-preview-248--vizarr.netlify.app/?source=https://raw.githubusercontent.com/tcompa/hosting-ome-zarr-on-github/refs/heads/main/20200812-CardiomyocyteDifferentiation14-Cycle1_mip.zarr/B/03/0

But the current main fails. Same for later dev builds, e.g.: https://deploy-preview-242--vizarr.netlify.app/?source=https://raw.githubusercontent.com/tcompa/hosting-ome-zarr-on-github/refs/heads/main/20200812-CardiomyocyteDifferentiation14-Cycle1_mip.zarr/B/03/0/

(earlier discussion on this here: fractal-analytics-platform/fractal-data#67)

[will-moore]

@dannda has noticed the same issue while working on a similar viewer at BioNGFF/biongff-viewer#13 with some more details there

[jluethi]

Thanks a lot @will-moore ! Also looks like the approach in BioNGFF/biongff-viewer#16 solves the issue for us.

Will you push the change upstream? @dannda (nice to virtually meet you!): What is your read on this issue? Do you see this as something that will get fixed again in Chromium or something that would make sense to be in Vizarr?

[dannda]

Nice to meet you @jluethi ! I was a bit unsure about the issue as it is a reported bug so it should get fixed in Chromium, but I'm completely clueless on what the timescales could be for that to happen. So maybe it is worth pushing upstream while we wait for the fix