[Dawn + Tint] Compiler encountered an internal error

[Marcin Mat]

Hi, a user reported a compiler error when using Chrome on an Apple device (based on mention to RenderPipelineMTL.mm line 445). I do not have full details as the GitHub issue was just created. I understand this is not much to go from, so I've added a link to the orginal report.

• Link to GitHub issue: https://github.com/Scthe/nanite-webgpu/issues/7
• Link to application source code: https://github.com/Scthe/nanite-webgpu
• Link to deployed application: https://scthe.github.io/nanite-webgpu/

[Corentin Wallez]

Hey Marcin!

Thanks for the report. This seems like a Metal internal compiler error reported here. I'll chime in on the issue, but the best channel to report errors is https://issues.chromium.org/ with the "WebGPU" component and the report from about:gpu is often necessary as issues are often GPU / OS / ... specific. In this case knowing which pipeline causes the issue would also help. Our error messages should contain the pipeline label but we missed it in this case, so I'll file an issue to improve this.

The Nanite demo and hair rendering demos were quite cool, do you research directly using WebGPU or is it only once you have results to have shareable demos for papers? (and yes for atomic<u64>, it is a VERY requested feature and will be up there when we start adding more)

Cheers,

Corentin

--
You received this message because you are subscribed to the Google Groups "Dawn Graphics" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dawn-graphic...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dawn-graphics/e9fb0eba-c30f-4af2-a25b-5a041e951bc2n%40googlegroups.com.

[Marcin Mat]

Hi,

thank you for your quick response. From what I see, https://source.chromium.org/chromium/chromium/src/+/main:third_party/dawn/src/dawn/native/metal/RenderPipelineMTL.mm;drc=fab658d209f09779c7e2f90fb34cebdf7ded681e;l=444 only rethrows an error if the pipeline creation failed.

This error can happen only on Apple devices, and I don't own one. The problem was reported by the user and due to lack of hardware I am not able to reproduce it. I can ask them to report an issue in Chromium's bug tracker (to provide about:gpu that you've mentioned), but I would also understand if they refused. My project is open source and any help I get is voluntary. I also see that submitting an issue requires a Google account, which for many people is a no-go.

As for which shader caused the problem, all the pipelines in the app already have labels. The error message provided by Chrome does not contain any more info I could interpret.

For the last question, I'm not sure I understand would you mean by "The Nanite demo and hair rendering demos were quite cool, do you research directly using WebGPU or is it only once you have results to have shareable demos for papers?". Both apps were developed using WebGPU from the start. You can check commit history if you are interested in a full timeline.

Cheers,
Marcin

[Corentin Wallez]

On Tue, Sep 10, 2024 at 1:47 AM Marcin Mat <marci...@gmail.com> wrote:

Hi,

thank you for your quick response. From what I see, https://source.chromium.org/chromium/chromium/src/+/main:third_party/dawn/src/dawn/native/metal/RenderPipelineMTL.mm;drc=fab658d209f09779c7e2f90fb34cebdf7ded681e;l=444 only rethrows an error if the pipeline creation failed.

Yes, I opened an issue to fix this as well.

 

This error can happen only on Apple devices, and I don't own one. The problem was reported by the user and due to lack of hardware I am not able to reproduce it. I can ask them to report an issue in Chromium's bug tracker (to provide about:gpu that you've mentioned), but I would also understand if they refused. My project is open source and any help I get is voluntary. I also see that submitting an issue requires a Google account, which for many people is a no-go.

And thank you for reporting the issue here! We appreciate folks taking time to report issues, but even if they don't, hopefully as we keep making the WebGPU implementation more robust, their issues will be fixed as we fix other reports. Note that filing issues doesn't require a GMail address, but just registering like on other websites.

As for which shader caused the problem, all the pipelines in the app already have labels. The error message provided by Chrome does not contain any more info I could interpret.

For the last question, I'm not sure I understand would you mean by "The Nanite demo and hair rendering demos were quite cool, do you research directly using WebGPU or is it only once you have results to have shareable demos for papers?". Both apps were developed using WebGPU from the start. You can check commit history if you are interested in a full timeline.
 

Cheers,
Marcin

Cheers,

Corentin

 

On Monday 9 September 2024 at 12:00:46 UTC+2 cwa...@google.com wrote:

Hey Marcin!

Thanks for the report. This seems like a Metal internal compiler error reported here. I'll chime in on the issue, but the best channel to report errors is https://issues.chromium.org/ with the "WebGPU" component and the report from about:gpu is often necessary as issues are often GPU / OS / ... specific. In this case knowing which pipeline causes the issue would also help. Our error messages should contain the pipeline label but we missed it in this case, so I'll file an issue to improve this.

The Nanite demo and hair rendering demos were quite cool, do you research directly using WebGPU or is it only once you have results to have shareable demos for papers? (and yes for atomic<u64>, it is a VERY requested feature and will be up there when we start adding more)

Cheers,

Corentin

On Mon, Sep 9, 2024 at 9:46 AM Marcin Mat <marci...@gmail.com> wrote:

Hi, a user reported a compiler error when using Chrome on an Apple device (based on mention to RenderPipelineMTL.mm line 445). I do not have full details as the GitHub issue was just created. I understand this is not much to go from, so I've added a link to the orginal report.

• Link to GitHub issue: https://github.com/Scthe/nanite-webgpu/issues/7
• Link to application source code: https://github.com/Scthe/nanite-webgpu
• Link to deployed application: https://scthe.github.io/nanite-webgpu/

--
You received this message because you are subscribed to the Google Groups "Dawn Graphics" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dawn-graphic...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dawn-graphics/e9fb0eba-c30f-4af2-a25b-5a041e951bc2n%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Dawn Graphics" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dawn-graphic...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/dawn-graphics/58b03a60-bc7e-4748-b60b-94a26592a388n%40googlegroups.com.

[Ken Russell]

Hi Marcin,

On Mon, Sep 9, 2024 at 4:47 PM Marcin Mat <marci...@gmail.com> wrote:

Hi,

thank you for your quick response. From what I see, https://source.chromium.org/chromium/chromium/src/+/main:third_party/dawn/src/dawn/native/metal/RenderPipelineMTL.mm;drc=fab658d209f09779c7e2f90fb34cebdf7ded681e;l=444 only rethrows an error if the pipeline creation failed.

This error can happen only on Apple devices, and I don't own one. The problem was reported by the user and due to lack of hardware I am not able to reproduce it. I can ask them to report an issue in Chromium's bug tracker (to provide about:gpu that you've mentioned), but I would also understand if they refused. My project is open source and any help I get is voluntary. I also see that submitting an issue requires a Google account, which for many people is a no-go.

As for which shader caused the problem, all the pipelines in the app already have labels. The error message provided by Chrome does not contain any more info I could interpret.

For the last question, I'm not sure I understand would you mean by "The Nanite demo and hair rendering demos were quite cool, do you research directly using WebGPU or is it only once you have results to have shareable demos for papers?". Both apps were developed using WebGPU from the start. You can check commit history if you are interested in a full timeline.

Our team just thought it was very nice to see your ground-up implementation of these algorithms in WebGPU. Up to this point, many larger rendering algorithms and engines running on top of WebGPU have been ports of existing C++ code bases, like Unity's. Also, in the past, research groups have done web ports of their code to make it easier to share their techniques with larger audiences.

Anyway, looking forward to collaborating to help your projects run seamlessly across browsers and operating systems.

Best,

-Ken

Cheers,
Marcin

On Monday 9 September 2024 at 12:00:46 UTC+2 cwa...@google.com wrote:

Hey Marcin!

Thanks for the report. This seems like a Metal internal compiler error reported here. I'll chime in on the issue, but the best channel to report errors is https://issues.chromium.org/ with the "WebGPU" component and the report from about:gpu is often necessary as issues are often GPU / OS / ... specific. In this case knowing which pipeline causes the issue would also help. Our error messages should contain the pipeline label but we missed it in this case, so I'll file an issue to improve this.

The Nanite demo and hair rendering demos were quite cool, do you research directly using WebGPU or is it only once you have results to have shareable demos for papers? (and yes for atomic<u64>, it is a VERY requested feature and will be up there when we start adding more)

Cheers,

Corentin

On Mon, Sep 9, 2024 at 9:46 AM Marcin Mat <marci...@gmail.com> wrote:

Hi, a user reported a compiler error when using Chrome on an Apple device (based on mention to RenderPipelineMTL.mm line 445). I do not have full details as the GitHub issue was just created. I understand this is not much to go from, so I've added a link to the orginal report.

• Link to GitHub issue: https://github.com/Scthe/nanite-webgpu/issues/7
• Link to application source code: https://github.com/Scthe/nanite-webgpu
• Link to deployed application: https://scthe.github.io/nanite-webgpu/

--
You received this message because you are subscribed to the Google Groups "Dawn Graphics" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dawn-graphic...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dawn-graphics/e9fb0eba-c30f-4af2-a25b-5a041e951bc2n%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Dawn Graphics" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dawn-graphic...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/dawn-graphics/58b03a60-bc7e-4748-b60b-94a26592a388n%40googlegroups.com.

[Marcin Mat]

Hi,

I've created https://issues.chromium.org/issues/365957553 which summarises all the info we have. It also includes "about:gpu" log from the affected user. Not sure why it was assigned to "Chromium > Blink > WebGPU" component, but there does not seem to be an edit option. If you want, you can close this group conversation - the issue report should be sufficient for discussions?

Cheers,

Marcin