Playground: WebGPU gpu memory leak

Bugs
,
1

Environment:
Windows 10 x64
Chromium 111.0.5563.65 x64 (ungoogled-chromium build) with WebGPU enabled
Nvidia GTX 1060 6GB Notebook
Babylon.js 5.50.1

Steps:

  1. Open a playground with WebGPU
    https://playground.babylonjs.com/?webgpu#SYQW69#1092
  2. Check gpu memory, where about 1.1GB used
    ๅ›พ็‰‡
    ๅ›พ็‰‡1323ร—862 104 KB
  3. Check the run button and wait for load completed
    ๅ›พ็‰‡
  4. Repeat 3 for 6 times
  5. Check gpu memory, which would never released unless tab is closed or reloaded
    ๅ›พ็‰‡
    ๅ›พ็‰‡1555ร—690 112 KB

The GPU memory usage of a chrome process after all the steps:

ๅ›พ็‰‡
ๅ›พ็‰‡584ร—615 5.47 KB

2

ping @Evgeni_Popov

3

I donโ€™t reproduce, I start at 3.1/12Gb and after 10 runs Iโ€™m still at 3.1/12Gb.

Keep in mind that WebGPU support is not yet fully implemented in browsers, and there are still some bugs (for example on our Ocean demo: 1701 - dawn - Implementation of the WebGPU standard - Monorail).

1 Like
4

Here is screen recording for this:

Would anything from chrome://gpu helps? This is too large to be pasted into reply.
report.zip (13.8 KB)

6

I do reproduce today! Going to have a look.

3 Likes
7

Memory leaks (among others) will be corrected by :

4 Likes