[Bug] Crash on intel iGPU with latest drivers

[v-romanov]

Bug description

On Windows 11 with latest intel GPU drivers (tested on HD 620 with version 27.20.100.8984 and Iris X with version 30.01.101.3111) at every second time browser went black and shader compiling is failed.

Minimal example: https://github.com/v-romanov/vtk-js-intel-igpu-crash

Steps to reproduce

Load large enough volume as in:
https://github.com/v-romanov/vtk-js-intel-igpu-crash

Detailed Behavior

Every second time browser went black and errors about shader compilation and/or webgl context missing.

Expected Behavior

Like ever another second time execution which went normal.

Environment

• vtk.js version: 32.14.0
• Browsers: Edge, Chrome
• OS: Windows 11 (Another not tested)
• GPU: Intel integrated

[finetjul]

Can you paste the console errors you have (that helps when searching issues)

[v-romanov]

Yes, of course.

main.js:79 Loading file
main.js:83 Convering file
main.js:91 Apply to VTK
main.js:100  Error compiling shader '#version 300 es
#define attribute in
#define textureCube texture
#define texture2D texture
#define textureCubeLod textureLod
#define texture2DLod textureLod


#ifdef GL_FRAGMENT_PRECISION_HIGH
precision highp float;
precision highp int;
#else
precision mediump float;
precision mediump int;
#endif

/*=========================================================================

  Program:   Visualization Toolkit
  Module:    vtkPolyDataVS.glsl

  Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen
  All rights reserved.
  See Copyright.txt or http://www.kitware.com/Copyright.htm for details.

     This software is distributed WITHOUT ANY WARRANTY; without even
     the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
     PURPOSE.  See the above copyright notice for more information.

=========================================================================*/

attribute vec4 vertexDC;

out vec3 vertexVCVSOutput;
uniform mat4 PCVCMatrix;

uniform float dcxmin;
uniform float dcxmax;
uniform float dcymin;
uniform float dcymax;

void main()
{
  // dcsmall is the device coords reduced to the
  // x y area covered by the volume
  vec4 dcsmall = vec4(
    dcxmin + 0.5 * (vertexDC.x + 1.0) * (dcxmax - dcxmin),
    dcymin + 0.5 * (vertexDC.y + 1.0) * (dcymax - dcymin),
    vertexDC.z,
    vertexDC.w);
  vec4 vcpos = PCVCMatrix * dcsmall;
  vertexVCVSOutput = vcpos.xyz/vcpos.w;
  gl_Position = dcsmall;
}
': 
vtkErrorMacro @ macros2.js:50
publicAPI.compile @ Shader.js:45
publicAPI.compileShader @ ShaderProgram.js:37
publicAPI.readyShaderProgram @ ShaderCache.js:79
publicAPI.readyShaderProgramArray @ ShaderCache.js:71
publicAPI.updateShaders @ VolumeMapper.js:385
publicAPI.renderPieceDraw @ VolumeMapper.js:937
publicAPI.renderPiece @ VolumeMapper.js:1003
publicAPI.volumePass @ VolumeMapper.js:152
publicAPI.apply @ ViewNode.js:41
publicAPI.traverse @ ViewNode.js:32
publicAPI.traverseVolumePass @ Volume.js:41
publicAPI.traverse @ ViewNode.js:27
publicAPI.traverse @ ViewNode.js:34
publicAPI.traverse @ ForwardPass.js:84
publicAPI.traverseAllPasses @ RenderWindow.js:572
forceRender @ RenderWindowInteractor.js:410
publicAPI.render @ RenderWindowInteractor.js:803
publicAPI.render @ RenderWindow.js:89
afterAll @ main.js:100
await in afterAll
(anonymous) @ main.js:68
main.js:100  0: #version 300 es
1: #define attribute in
2: #define textureCube texture
3: #define texture2D texture
4: #define textureCubeLod textureLod
5: #define texture2DLod textureLod
6: 
7: 
8: #ifdef GL_FRAGMENT_PRECISION_HIGH
9: precision highp float;
10: precision highp int;
11: #else
12: precision mediump float;
13: precision mediump int;
14: #endif
15: 
16: /*=========================================================================
17: 
18:   Program:   Visualization Toolkit
19:   Module:    vtkPolyDataVS.glsl
20: 
21:   Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen
22:   All rights reserved.
23:   See Copyright.txt or http://www.kitware.com/Copyright.htm for details.
24: 
25:      This software is distributed WITHOUT ANY WARRANTY; without even
26:      the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
27:      PURPOSE.  See the above copyright notice for more information.
28: 
29: =========================================================================*/
30: 
31: attribute vec4 vertexDC;
32: 
33: out vec3 vertexVCVSOutput;
34: uniform mat4 PCVCMatrix;
35: 
36: uniform float dcxmin;
37: uniform float dcxmax;
38: uniform float dcymin;
39: uniform float dcymax;
40: 
41: void main()
42: {
43:   // dcsmall is the device coords reduced to the
44:   // x y area covered by the volume
45:   vec4 dcsmall = vec4(
46:     dcxmin + 0.5 * (vertexDC.x + 1.0) * (dcxmax - dcxmin),
47:     dcymin + 0.5 * (vertexDC.y + 1.0) * (dcymax - dcymin),
48:     vertexDC.z,
49:     vertexDC.w);
50:   vec4 vcpos = PCVCMatrix * dcsmall;
51:   vertexVCVSOutput = vcpos.xyz/vcpos.w;
52:   gl_Position = dcsmall;
53: }
54:

vtkErrorMacro @ macros2.js:50
publicAPI.compileShader @ ShaderProgram.js:38
publicAPI.readyShaderProgram @ ShaderCache.js:79
publicAPI.readyShaderProgramArray @ ShaderCache.js:71
publicAPI.updateShaders @ VolumeMapper.js:385
publicAPI.renderPieceDraw @ VolumeMapper.js:937
publicAPI.renderPiece @ VolumeMapper.js:1003
publicAPI.volumePass @ VolumeMapper.js:152
publicAPI.apply @ ViewNode.js:41
publicAPI.traverse @ ViewNode.js:32
publicAPI.traverseVolumePass @ Volume.js:41
publicAPI.traverse @ ViewNode.js:27
publicAPI.traverse @ ViewNode.js:34
publicAPI.traverse @ ForwardPass.js:84
publicAPI.traverseAllPasses @ RenderWindow.js:572
forceRender @ RenderWindowInteractor.js:410
publicAPI.render @ RenderWindowInteractor.js:803
publicAPI.render @ RenderWindow.js:89
afterAll @ main.js:100
await in afterAll
(anonymous) @ main.js:68
main.js:100  
vtkErrorMacro @ macros2.js:50
publicAPI.compileShader @ ShaderProgram.js:39
publicAPI.readyShaderProgram @ ShaderCache.js:79
publicAPI.readyShaderProgramArray @ ShaderCache.js:71
publicAPI.updateShaders @ VolumeMapper.js:385
publicAPI.renderPieceDraw @ VolumeMapper.js:937
publicAPI.renderPiece @ VolumeMapper.js:1003
publicAPI.volumePass @ VolumeMapper.js:152
publicAPI.apply @ ViewNode.js:41
publicAPI.traverse @ ViewNode.js:32
publicAPI.traverseVolumePass @ Volume.js:41
publicAPI.traverse @ ViewNode.js:27
publicAPI.traverse @ ViewNode.js:34
publicAPI.traverse @ ForwardPass.js:84
publicAPI.traverseAllPasses @ RenderWindow.js:572
forceRender @ RenderWindowInteractor.js:410
publicAPI.render @ RenderWindowInteractor.js:803
publicAPI.render @ RenderWindow.js:89
afterAll @ main.js:100
await in afterAll
(anonymous) @ main.js:68
192.168.187.129/:1  WebGL: CONTEXT_LOST_WEBGL: loseContext: context lost
VolumeMapper.js:407  Uncaught (in promise) TypeError: Cannot read properties of null (reading 'isAttributeUsed')
    at publicAPI.setMapperShaderParameters (VolumeMapper.js:407:19)
    at publicAPI.updateShaders (VolumeMapper.js:398:15)
    at publicAPI.renderPieceDraw (VolumeMapper.js:937:15)
    at publicAPI.renderPiece (VolumeMapper.js:1003:15)
    at publicAPI.volumePass (VolumeMapper.js:152:17)
    at publicAPI.apply (ViewNode.js:41:7)
    at publicAPI.traverse (ViewNode.js:32:15)
    at publicAPI.traverseVolumePass (Volume.js:41:23)
    at publicAPI.traverse (ViewNode.js:27:7)
    at publicAPI.traverse (ViewNode.js:34:29)
publicAPI.setMapperShaderParameters @ VolumeMapper.js:407
publicAPI.updateShaders @ VolumeMapper.js:398
publicAPI.renderPieceDraw @ VolumeMapper.js:937
publicAPI.renderPiece @ VolumeMapper.js:1003
publicAPI.volumePass @ VolumeMapper.js:152
publicAPI.apply @ ViewNode.js:41
publicAPI.traverse @ ViewNode.js:32
publicAPI.traverseVolumePass @ Volume.js:41
publicAPI.traverse @ ViewNode.js:27
publicAPI.traverse @ ViewNode.js:34
publicAPI.traverse @ ForwardPass.js:84
publicAPI.traverseAllPasses @ RenderWindow.js:572
forceRender @ RenderWindowInteractor.js:410
publicAPI.render @ RenderWindowInteractor.js:803
publicAPI.render @ RenderWindow.js:89
afterAll @ main.js:100
await in afterAll
(anonymous) @ main.js:68

[finetjul]

Thanks, there is not much information indeed.

[daker]

Try to change the ANGLE graphics backend using chrome://flags/#use-angle

[v-romanov]

@daker

OpenGL - still crashes
DirectX 11 - still crashes
DirectX 9 - still crashes and more errors
DirectX 11 on 12 - works fine. on both GPU as I tested.

So for any user is only option to advise them to switch to D3D11on12?

[daker]

i believe so or you can set Chrome to use the high performance GPU if you have Intel & Nvidia

[v-romanov]

Where is still no solution for systems with only Intel iGPU, and something like a year ago there is no such problem, I updated my drivers a week ago and get those crashes.

Is where any way to shrink gl code to minimal which reproduce problem for reporting it to Chrome or Intel?

[v-romanov]

Do you have an estimate on when it might be fixed?

[daker]

The rendering pipeline vtk.js didn't change, so this is a bug in the driver or in Chrome, i would recommend rolling back the driver (and chrome ?) to narrow down the versions then report the bug to the appropriate project.

[v-romanov]

I updated repo with sync data instead of dcm file, so it easy to clone run.

And also I detected exact line of code which cause WebGL problem:

vtk-js/Sources/Rendering/OpenGL/Texture/index.js

Line 1681 in f6a5541

model.context.texSubImage3D(

50 % times it lost context.

I tried small snippet to recreate part of gl code:

function testTexSubImage3D() {
  // Set up WebGL context
  const canvas = document.createElement("canvas");
  const gl = canvas.getContext("webgl2");

  if (!gl) {
    console.error("WebGL 2 not supported");
    return;
  }

  const model = {
    target: gl.TEXTURE_3D,
    width: 600,
    height: 600,
    depth: 600,
  };

  // Create a 3D texture
  const texture = gl.createTexture();
  gl.bindTexture(model.target, texture);

  gl.pixelStorei(gl.UNPACK_ALIGNMENT, 1);

  gl.texStorage3D(
    model.target,
    1,
    gl.R32F,
    model.width,
    model.height,
    model.depth,
  );

  const data = new Float32Array(model.width * model.height * model.depth);

  try {
    gl.texSubImage3D(
      model.target,
      0, // mipmap level
      0,
      0,
      0, // xoffset, yoffset, zoffset
      model.width,
      model.height,
      model.depth,
      gl.RED, // 6403 = gl.RED
      gl.FLOAT, // 5126 = gl.FLOAT
      data,
    );
    console.log("texSubImage3D call succeeded");

    return true;
  } catch (error) {
    console.error("texSubImage3D failed:", error);
    return false;
  }
}

testTexSubImage3D();

But it's never lost WebGL.

So I don't sure that if I report bug with vtk-js repo demo, someone from Intel/Chromium will dig into vtk-js by they self.

Also I have new errors messages:

main.js:103 [.WebGL-0x501400921500] GL_INVALID_OPERATION: Error: 0x00000502, in ..\..\third_party\angle\src\libANGLE\renderer\d3d\d3d11\ResourceManager11.cpp, rx::ResourceManager11::allocate:496. Internal D3D11 error: HRESULT: 0x887A0005 (removal reason: HRESULT: 0x887A0020): Error allocating ShaderResourceView

and

localhost/:1  WebGL: CONTEXT_LOST_WEBGL: loseContext: context lost
localhost/:1  [GroupMarkerNotSet(crbug.com/242999)!:A00025009C200000]Automatic fallback to software WebGL has been deprecated. Please use the --enable-unsafe-swiftshader flag to opt in to lower security guarantees for trusted content.
localhost/:1  [.WebGL-0x3f04000e1b00]GL Driver Message (OpenGL, Performance, GL_CLOSE_PATH_NV, High): GPU stall due to ReadPixels

At the end, do you have any small gl snippets which recreate vtk-js medium behaviour? Or ways to record webgl calls at run?

[daker]

On Windows you can try Microsoft PIX https://developer.playcanvas.com/user-manual/optimization/gpu-profiling/#webgl-and-webgpu-applications-on-windows

[finetjul]

• The line you mention where it crashes is actually a line that was recently changed. You might want to try with a slightly older VTK.js (<32.12) to see if it still breaks.
• Could it also be that your texture got resized over time ?
• 600x600x600 is not a small volume. Do you have the same crash when scalars are UCHAR instead of UINT16 ?

[v-romanov]

@finetjul

1. there is problem even back in 30.10.0.
2. No, as you can see in demo project, there is no any changes to mapper
3. It was all fine with 600 mb dcm files before new Intel drivers, and it's still fine with 768x768x768 2bytes volume in ThreeJS. UCHAR is not my target, and as I see vtk-js anyway upload to GPU Float32Array.

with D3D11on12 GPU shared RAM is okay, like 1.5 GB and on refresh it's cleared fine.

But with D3D11 on first run memory almost out, like 3.5 of 3.9. On refresh it's not cleared, another allocation takes place, out of memory, context lost, memory back to normal, and then we have errors with shaders compilation as above because we pointing to old context.