[Bug] 2.6.4: sampler array element still unresolved when the index is not constant
Los mantenedores suelen responder en 2 días
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 42/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- rust
Línea de trabajo
Start by reading sampler_array.rs and the changes for #426 to understand how constant sampler array indices are lowered. Then trace how a dynamic index inside a two-light loop is represented and check whether it produces a LocalPointerFieldLoad fact; the report has no shader dump or named test, so reproducing the failure may require obtaining a module from the reporter. Done means the reported shadowed material compiles without the Metal sampler error or WebGL context loss.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Send logs report ID
Nothing that app can log
Where does it go wrong?
An app or game
What happens
Follow-up to #426. The sampler array itself is now accepted, but this shader still
loses its WebGL context one step later.
Setup
- NullMoth 2.6.4 (
com.nullmoth.NVRM (2.6.4)) - macOS 26.7.2 (25G332)
- NVIDIA GeForce RTX 5050 Laptop GPU (10de:2d98), 8 GB
- Brave 156.1.98.60 (Chromium 156.0.8078.48, ANGLE Metal), WebGL2
App
"Car Soccer", a three.js game served locally. It renders fine on 2.6.4 with
shadowMap.enabled = false; with shadows enabled the context is lost while
compiling the first shadowed material.
Error
GL error: HIGH: Error: 0x00000502, in ../../third_party/angle/src/libANGLE/renderer/metal/mtl_utils.mm, CreateMslShader:1620. Internal error. Metal error: sampler operand is a pointer whose exact sampler state was not recovered; retry with helpers inlined and object fields forwarded: sampler operand is a pointer whose exact sampler state was not recovered; as ordinary samplers: sampler operand is a pointer whose exact sampler state was not recovered then
GL_INVALID_OPERATION: Error: 0x00000502, ... CreateMslShader:1620. ... GL_CONTEXT_LOST_KHR: glCreateProgram: Context has been lost.
2 CreateMslShader failures and 28 GL_CONTEXT_LOST lines per page load.
Materials reported by three.js: Basalt, Concrete / field side,
Inner fascia / field side — MeshStandardMaterial, lit, shadowed.
On 2.6.3 the same shader failed earlier, with
entry parameter 15 is an array of 2 samplers, which this translator has no descriptor-array lowering for; ..., so 2.6.4 does bind the array.
Unverified guess
sampler_array.rs says only a constant element index is lowered. This shader
indexes the array inside a two-light loop, so the element load may not produce a
LocalPointerFieldLoad fact and the placeholder survives. If so, this is the
dynamic-index case rather than the constant-index case fixed in #426.
Dump attempts
METAL2VULKAN_REPRO_DIR=<dir> and METAL2VULKAN_RETRY_DEBUG=1 exported before
launching the browser produced no repro bundle (the directory stayed empty), so I
cannot attach the failing module.
Happy to test a build or run with any dump variable you suggest.
Written by you
- I wrote this report myself. AI-written issues are closed without review (see CONTRIBUTING.md).
App or game (if it is one)
Any chromium browser
Did you change anything yourself?
No response
- Lenguaje dominante
- Rust
- Estrellas
- 2.5k
- Forks
- 233
- Merge medio
- 3 d 14 h
- PR fusionados (30 d)
- 14
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de nullmoth/nvidia-macos-driver
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
nullmoth/nvidia-macos-driver#141 · 1 comentario ·
Los mantenedores suelen responder en 2 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 73/100
nullmoth/nvidia-macos-driver#28 ·
Los mantenedores suelen responder en 2 días
-
bug
Dificultad 5/5 Más de una semana Aptitud para principiantes 20/100
nullmoth/nvidia-macos-driver#452 ·
Los mantenedores suelen responder en 2 días
-
bug
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
nullmoth/nvidia-macos-driver#451 ·
Los mantenedores suelen responder en 2 días
-
bug
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
nullmoth/nvidia-macos-driver#430 ·
Los mantenedores suelen responder en 2 días
Todos los issues de nullmoth/nvidia-macos-driver
Issues similares
-
bug priority: low ui
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
storytold/photocraft#10370 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
area:doc bug in progress needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
bherbruck/solvecraft#9634 · 2 comentarios · 1 reacción ·
-
inflate: total_in uses plain += on c_ulong (32-bit on Windows), panics in debug for streams > 4 GiBAbierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 85/100
trifectatechfoundation/zlib-rs#570 · 1 comentario ·
-
bug discord-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
LanternOps/breeze#10755 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
aranya-project/aranya#803 ·