The first real session reported WARNING: 1 RID of type "Texture" was leaked. at: finalize (servers/rendering/rendering_device.cpp:9137) cleanup() frees every buffer but knew nothing about textures, because until the previous commit dc-terrain created none. Both atlas RIDs are freed now. ⚠ AND THAT WARNING IS THE VERIFICATION THE PREVIOUS COMMIT SAID IT LACKED. dc-terrain created NO textures before it, so a leaked Texture RID can only be the atlas: the code executes. The same log shows no uniform_set_create failure and chunks meshing, uploading and colliding normally throughout, so binding 14 is live and the density path is unaffected — which was the risk that commit flagged (a failed set makes every dispatch read nothing and looks like a wrong field rather than an error). I had been grepping a different log and reported the path unexecuted twice. The evidence was in the session's own output.