[Bug] Shader Compilation Error while visting deck.gl homepage
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 14.6k
- Forks
- 2.3k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 42
Description
Description
While visiting deck.gl homepage (or while running latest version of the library locally) I'm getting Shader Compilation Error in fragment solid-polygon-layer-fragment-shader inside LibreWolf. As far as I tested it does not happen on Chromium or Firefox.
So it might be an issue inside of the LibreWolf not deck.gl, but I'm not sure.
Flavors
- Script tag
- React
- Python/Jupyter notebook
- MapboxOverlay
- GoogleMapsOverlay
- CARTO
- ArcGIS
Expected Behavior
Visiting deck.gl should not throw compilation error.
Steps to Reproduce
Visit deck.gl on LibreWolf
Environment
- Framework version: deck.gl@9.1.12
- Browser: LibreWolf 138.0.1-2
- OS: Linux 6.14.6-arch1-1
Logs
Screenshot of the home page
Error from the console:
Uncaught (in promise) Error: Error during linking: Must have a compiled vertex shader attached:
SHADER_INFO_LOG:
0(62) : error C7532: global function uintBitsToFloat requires "#version 330" or later
0(62) : error C0000: ... or #extension GL_ARB_shader_bit_encoding : enable
0(62) : error C0000: ... or #extension GL_ARB_gpu_shader5 : enable
_reportLinkStatus https://deck.gl/assets/js/7771.61fb86c2.js:1
_linkShaders https://deck.gl/assets/js/7771.61fb86c2.js:1
ze https://deck.gl/assets/js/7771.61fb86c2.js:1
createRenderPipeline https://deck.gl/assets/js/7771.61fb86c2.js:1
createRenderPipeline https://deck.gl/assets/js/7771.61fb86c2.js:1
_updatePipeline https://deck.gl/assets/js/7771.61fb86c2.js:1
ft https://deck.gl/assets/js/7771.61fb86c2.js:1
_getModels https://deck.gl/assets/js/9dd8a0d2.6e1d733a.js:1
updateState https://deck.gl/assets/js/9dd8a0d2.6e1d733a.js:1
_update https://deck.gl/assets/js/9dd8a0d2.6e1d733a.js:1
_initialize https://deck.gl/assets/js/9dd8a0d2.6e1d733a.js:1
_initializeLayer https://deck.gl/assets/js/9dd8a0d2.6e1d733a.js:1
_updateSublayersRecursively https://deck.gl/assets/js/9dd8a0d2.6e1d733a.js:1
_updateSublayersRecursively https://deck.gl/assets/js/9dd8a0d2.6e1d733a.js:1
_updateLayers https://deck.gl/assets/js/9dd8a0d2.6e1d733a.js:1
setLayers https://deck.gl/assets/js/9dd8a0d2.6e1d733a.js:1
updateLayers https://deck.gl/assets/js/9dd8a0d2.6e1d733a.js:1
_onRenderFrame https://deck.gl/assets/js/9dd8a0d2.6e1d733a.js:1
_renderFrame https://deck.gl/assets/js/7771.61fb86c2.js:1
redraw https://deck.gl/assets/js/7771.61fb86c2.js:1
_animationFrame https://deck.gl/assets/js/7771.61fb86c2.js:1
[7771.61fb86c2.js:1:276607](https://deck.gl/assets/js/7771.61fb86c2.js)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the shader compilation error on the deck.gl homepage in LibreWolf 138.0.1-2, then compare it with Chromium and Firefox. Start from the reported solid-polygon-layer-fragment-shader failure and the _linkShaders/createRenderPipeline entries in assets/js/7771.61fb86c2.js; done means the homepage renders without this error or the browser-specific limitation is clearly established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- computer-graphics, data-visualization, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100