vtk-wasm webgl crashes with latest vtk-wasm docker images

Web
1

Hi,

I have been observing regular vtk-wasm crashes with webgl losing context because of bad memory allocation as shown in the below picture.

image

This was never occurring with the older docker images with version tag 9.6, I am observing this behaviour ever since the vtk 9.7 tags are released.

My setup is similar to how the Geometry Viewer example is setup, so i tried to replicate the same issue with the official example build.

I have observed that I get the same crash as the above picture when the camera orientation widget is on. If it is off or never used, I don’t see the crash happening.

I am uploading the example code with the sample vtp file to replicate the crash.

I have tested the uploaded code both for the latest version docker image and also the tag 9.6.20260522-05a3785034, I have observed crash in latest tag but not in the 9.6 version tag.

example.zip (390.7 KB)

After building example, load the vtp file and try to interact more to rotate, pan and zoom for the crash to occur.

Webgpu renderer does not have any crashes, however I face different issues with transparent actors, plane widgets there, I have also observed the webgpu renderer in vtk wasm doesnt render the surfaces generated by the vtkRuledSurfaceFilter class and my actors with opacity look so different when compared to the webgl background. I have setup webgpu similar to the GeometryViewer example as above so could you please let me know if there is wrong with the setup or the example? or since webgpu is still in experimental stage these isssues are common?

Thank you

2

this could be happening for similar reasons as https://gitlab.kitware.com/vtk/vtk/-/work_items/20121. Maybe the buffer cache keeps growing indefinitely.

3

I downloaded and built your example, cannot reproduce the context lost message. I still think it’s the cache issue. What GPU did you see this on?

4

Its NVIDIA GeForce RTX 4060 Laptop GPU and I observe this error consistently only when the camera orientation widget is present, when it is turned off It never crashes. Another thing to note is the crash happens only after some interactions with the geometry

5

i’ve same gpu but desktop, and i tried interacting with the scene for upto 2 mins. didnt see that warning. is there another way to reproduce it?

6

Not really sure, I have this behaviour in NVIDIA RTX 4050 too but that is a laptop GPU as well, I will try to reproduce with desktop GPUs but it will take some time. Apart from that the only thing that comes to mind is to load multiple vtk actors instead of the current example that only loads one vtp.

7

I want to know if this is related to texture buffer cache or not.

So can you add these lines in GeometryViewer::Initialize function? The wasmOpenGLRenderWindow is scoped inside an else-if statement.

auto* state = wasmOpenGLRenderWindow->GetState();
state->SetArrayTextureBufferCache(nullptr);

If you still see the crash, then it means the issue lies elsewhere.

8

Yep, It is on the cache, I no longer see the error when I set the buffer cache to null and see the error again after commenting out these two lines.

9

Okay, that’s good to know. thanks for testing that.

i am working on capping the cache and evicting LRU vtkDataArray from the cache if the total size >= some reasonable size.

10

https://gitlab.kitware.com/vtk/vtk/-/merge_requests/13494 should address this problem.