Closed eyaler closed 3 weeks ago
We also hit this issue last Friday and the investigation is WIP. It looks like a regression in Chrome now. Stay tuned.
After more investigation, we think it's a DXC (shader compiler) issue. You may find more details at https://issues.chromium.org/issues/368997517. A workaround in ONNX Runtime, which Transformers.js is based on, is under review at https://github.com/microsoft/onnxruntime/pull/21995.
Could "range error - buffer allocation failed" be related to this? I'm seeing that error in Android Chrome after an update there.
Could "range error - buffer allocation failed" be related to this? I'm seeing that error in Android Chrome after an update there.
Your issue looks like OOM, and it's not related to this one, which crashes the GPU process. BTW, Google already fixed this issue in DXC, and the roll to Chrome will take place in a few days. We will ask if they could back port it to Chrome Stable.
alpha17 fixes this for me. thanks!
It seems fixed here too. Nice!
System Info
windows 64 tested with chrome 128,129,130beta and edge 128,129,130canary transformers v3alpha3-15 (also compared to 2.17.2)
Environment/Platform
Description
hi! i am running https://huggingface.co/Xenova/modnet with onnx-runtime web on webgpu (fp32 non-quantized model), with the following observations:
Failed to execute 'mapAsync' on 'GPUBuffer': A valid external Instance reference no longer exists.
Reproduction
You can see this in my following code. If necessary I can prepare a minimal example.
Compare the following with both transformers.js versions on both chromium 128 vs. 129/130 (approve the self-tab share and choose modnet from the dropdown)