GPU memory leak when enabling shadow maps

Questions
,
1

Hello,

I made a scene with a directional light, a plane receiving light, and a set of meshes that cast light.
The meshes are created dynamically and created and destroyed very often.
The more meshes I create and set their castShadows = true, the more my VRAM is getting filled. Eventhough I dispose the geometry, texture and material after removing the recent mesh.
This is done in order to play volumetric videos.
There is no memory leak if I do not enable shadow maps.

Is there something I am missing and not disposeing?
I am using MeshBasicMaterial for the dynamic meshes.

2

Not that I am aware of. Are you able to demonstrate the memory leak with a minimal test case (based on e.g. jsfiddle).

3

I tried to… but this editor… it makes no sense.
Look, one object has shadow, the other doesn’t.

So I wasn’t even able to make the sample, it already has weird bugs.

NoShadow
NoShadow2356×1267 93 KB

4

Ok solved the basic issue. just did castShadows in plural instead of castShadow.
I was not able to reproduce the memory leak for now.

5

How to set castShadows? There is only castShadow property.

6

castShadows does not exists. When using the correct castShadow property the fiddle works as expected.

https://jsfiddle.net/ueswhqmj/1/

7

I set the renderer shadowMap.enable = true、light castShadow = true、object the castShaow and receiveShadow as true. when i dispose the geometry, texture and m eterial, the memory is not released.

image
image1048×578 70.4 KB

image
image1180×502 68.9 KB

image

8

@liumu96 I suggest you demonstrate the memory leak with a live example.

And please keep in mind it’s sufficient to post once and not in multiple topics (Curiosity about glTF GPU memory footprint - #9 by liumu96).