Crashes sometimes

[takahirox]

The WebGPU devtools crashes sometimes. We need to investigate the root issue.

[mvaligursky]

I'm trying it with my webgpu code from local host on MacOS (Version 113.0.5672.63 (Official Build) (arm64)), and get this:

VM633:3 Uncaught (in promise) TypeError: t.context.createFramebuffer is not a function
    at new t (<anonymous>:3:528930)
    at e.initStateTrackers (<anonymous>:3:563295)
    at new e (<anonymous>:3:562328)
    at new e (<anonymous>:3:587904)
    at e.spyContext (<anonymous>:3:673808)
    at e.trigger (<anonymous>:3:395649)
    at HTMLCanvasElement.t (<anonymous>:3:595157)
    at callFunction (webgpu-devtools.bundle.js:634:23)
    at HTMLCanvasElement.getContext (webgpu-devtools.bundle.js:1892:63)
    at WebgpuGraphicsDevice._callee$ (webgpu-graphics-device.js:212:39)

webgpu-devtools.bundle.js:634:23 is this:

[mvaligursky]

Note: My crash went away eventually, and I cannot reproduce it currently.

[takahirox]

Thanks for the problem report. Sounds like it is a different issue from mine because mine is a crash on devtool panel. I will update the issue comment with details when I will encounter the issue again.

Would you mind opeining another issue?

About a problem you encountered,

TypeError: t.context.createFramebuffer is not a function

This is suspicious... Because, if I understand correctly, createFrameBuffer() is an API of WebGLRenderingContext, not GPUCanvasContext.

[mvaligursky]

createFrameBuffer() is an API of WebGLRenderingContext

Thanks for pointing this out, I figured it out. When I initialize the engine in WebGL mode, and trigger Spector JS (used to capture WebGL commands), and then switch to WebGPU, this is triggered. I guess we can ignore this, as this is not related to your plugin at all.