On this thread we figure out that I was facing a weird FPS drop because I was updating a disposed mesh, that makes me think, update a disposed mesh shouldn’t throws an error or at least a warning? :thinking:

@Alecell there is no reason to waste extra CPU cycles on this. It’s definitelly not a bug. You are responsible for your code and as I wrote you earlier here [image] Hard FPS lost when movin meshes There is a mesh.isDisposed() function available so if you are not sure whether your mesh is dispose…

Update a disposed object

Bugs

roland February 18, 2022, 9:24pm 2

@Alecell there is no reason to waste extra CPU cycles on this. It’s definitelly not a bug. You are responsible for your code and as I wrote you earlier here

you can easily check the disposal state of your meshes.

Topic		Replies	Views
Mesh.dispose trigger Uncaught TypeError: Cannot read property 'meshes' of null Bugs	10	1119	July 17, 2021
useMaterialMeshMap meshMap not cleaned up when a mesh is disposed Bugs	2	556	June 5, 2019
Default values of Material.dispose() arguments Questions	10	2145	July 24, 2019
Dispose doesn't free the memory Questions	10	2870	April 30, 2020
Ammo physics .dispose() on impact Questions	6	934	May 7, 2019

Update a disposed object

Related topics