Handling of unexpected errors in webgpu about servo HOT 2 OPEN

@highfive assign me

from servo.

In #32497 I thought we can use internal for such cases, but per spec it can only happen when creating pipelines. While some WebGPU stuff is failable (we can resolve promise rejected with IPC error or smth, although I am not sure if that would be per spec), most of them aren't as webgpu can operate with invalid objects, and sooner or later this invalid objects would be part of failable method call, where we can raise such error (or not).

That's essentially what we are doing now, ignoring errors (actually creating warning) thus resulting invalid objects, that should eventually reach fallible functions (where we currently also ignore errors), so maybe a macro or wrapper for IPC might not been such a bad idea after all.

In most cases, we can continue to do what we do now, but we need to further investigate if and how can we handle such errors as part of failable methods.

There are also some more edge cases (like IPC failures while dropping WebGPU objects).

from servo.