1860803 - Weird crashes if you open a webgpu demo in 30 background tabs in quick succession

Status: REOPENED

(Core :: Graphics: WebGPU, defect, P1)

Description

[Mayank Bansal]

Create fresh profile
Enable webgpu
Open the following webgpu demo in 14-15 background tabs : https://tellusim.com/demos/webgpu-20230515/interface_layer/main.html (Note that the demo itself doesnt work which is a known issue).

ER: Weird crashes
Example:
https://crash-stats.mozilla.org/report/index/64e84e85-ea2a-4df0-96e4-a95790231024
https://crash-stats.mozilla.org/report/index/02ff91bb-3a51-413f-8205-7c5530231024
https://crash-stats.mozilla.org/report/index/c0e0682c-b31c-4037-9949-7042c0231024
https://crash-stats.mozilla.org/report/index/d2ff3037-6746-42ea-92f4-de0800231024

I monitor the task manager and the highest Nightly process memory use never went above 200-300 MB. But feel free to classify this as a OOM and close as RESOLVED INVALID.

Comment 1

[Mayank Bansal]

cant repro after i restarted my machine.
Edit: Can repro again if I open 30 demo tabs in the background. The highest memory use of any Nightly process never goes above 300-400mb (and I have plenty of spare RAM)

Comment 2

[Mayank Bansal]

Reopening in case there is anything interesting here. If there is nothing, I will close in a while.
cc :jandem because one of the signatures is similar to bug 1808352

Comment 3

[Mayank Bansal]

[@ mozilla::dom::binding_detail::DoGetOrCreateDOMReflector ] and [@ mozilla::dom::JSStreamConsumer::WriteSegment ] appear as consistent crash signatures when I repro this crash.

Comment 4

[Andrew McCreight [:mccr8]]

The signature looks like DoGetOrCreateDOMReflector, but it seems like a null deref, so not quite the same as bug 1808352.

Comment 5

[Jim Blandy :jimb]

Mayank, are you able to monitor GPU memory usage while you do this? It may be that you have plenty of CPU memory but we exhaust GPU memory.

Comment 6

[Mayank Bansal]

(In reply to Jim Blandy :jimb from comment #5)

Mayank, are you able to monitor GPU memory usage while you do this? It may be that you have plenty of CPU memory but we exhaust GPU memory.

You were correct, the GPU memory is exhausted.
Whjen you open 15 webgpu tabs in the background, they take up some GPU RAM. Once you start going to each tab, then memory shoots up quickly. At the instant the browser crashes, the GPU memory was at its physical limit.

Comment 7

[Jim Coffey]

Attachment: same problem

Thanks from cugtextcorlawn1970.