Echo Weaver Posted October 21, 2025 Report Posted October 21, 2025 While rummaging in my log files trying to see if I could get info on a couple of game freezes I just experienced I noticed that client-debug.log reported "[VerboseDebug]" on a lot of lines. I'd guess that I have verbose logging on? Did I do that? Is there a way to turn it off? I think of verbose debugging as something that takes extra resources and should not be turned on unless you're looking for a bug. In particular, I saw a couple of log lines about sound files stating that the game may stutter. There's also this line: 21.10.2025 15:48:17 [Debug] Texture with texture id 67 is leaking memory, missing call to Dispose. Set env var TEXTURE_DEBUG_DISPOSE to get allocation trace. Has anyone worked with this? Will setting the environment variable tell me what (presumably) mod uses texture ID 67? 1
Thorfinn Posted October 21, 2025 Report Posted October 21, 2025 (edited) Go to settings, and see if one of the header tabs is Dev. If so, just deselect Extended Debug Info. You might also have to look at the Interface tab and deselect Developer mode. [EDIT] I always enable it, because then it tells you the name of the block you are looking at. Otherwise you have to search through the .jsons to try to find its internal name. [EDIT2] In this particular case, if you enable VAO or texture (I forget which throws that message), you can find out what's causing the problem. Edited October 21, 2025 by Thorfinn
Echo Weaver Posted October 21, 2025 Author Report Posted October 21, 2025 (edited) 52 minutes ago, Thorfinn said: Go to settings, and see if one of the header tabs is Dev. If so, just deselect Extended Debug Info. You might also have to look at the Interface tab and deselect Developer mode. [EDIT] I always enable it, because then it tells you the name of the block you are looking at. Otherwise you have to search through the .jsons to try to find its internal name. [EDIT2] In this particular case, if you enable VAO or texture (I forget which throws that message), you can find out what's causing the problem. I've been toggling back and forth checking for exactly that -- the name of some blocks I was messing with mods for. This was my first thought, but dev mod is off. I've only ever used Extended Debug info, so perhaps it doesn't get fully turned off if I uncheck dev mode without turning it off first? I'll try turning on debug mode, check-then-uncheck Extended Debug Info, and turning dev mode back off. I only turn on dev mode if I want something from it because of aforementioned performance concerns. I'll try the other settings to go hunting for that texture id. ETA: Nope, that didn't stop it. I'm curious -- do you get VerboseDebug logging when you have dev mode turned off? Wondering if this is a Mac thing. Edited October 21, 2025 by Echo Weaver
Solution LadyWYT Posted October 22, 2025 Solution Report Posted October 22, 2025 19 hours ago, Thorfinn said: In this particular case, if you enable VAO or texture (I forget which throws that message), you can find out what's causing the problem. It should be the VAO option--that's the one I've used while hunting memory leaks. Make sure you check that option every time before loading the world, as it does seem to like to turn itself off. 18 hours ago, Echo Weaver said: ETA: Nope, that didn't stop it. I'm curious -- do you get VerboseDebug logging when you have dev mode turned off? Wondering if this is a Mac thing. I get it on PC with Dev mode off, so I don't think it's just a Mac thing. I don't recall if there was anything I did to enable it though...I figure it just kinda happens automatically.
Echo Weaver Posted October 22, 2025 Author Report Posted October 22, 2025 5 hours ago, LadyWYT said: It should be the VAO option--that's the one I've used while hunting memory leaks. Make sure you check that option every time before loading the world, as it does seem to like to turn itself off. So how does VAO and how does it point me to the mod with the bad image? 5 hours ago, LadyWYT said: I get it on PC with Dev mode off, so I don't think it's just a Mac thing. I don't recall if there was anything I did to enable it though...I figure it just kinda happens automatically. OK, great. That helps a lot. As has stated in several threads, VS on Mac has gotten weird since 1.21. The assumption is that it's primarily about the .Net upgrade, but when something like this pops up that doesn't behave how I expect, it's worth knowing that it's not just Macs.
LadyWYT Posted October 22, 2025 Report Posted October 22, 2025 49 minutes ago, Echo Weaver said: So how does VAO and how does it point me to the mod with the bad image? Honestly, I have no idea how it actually works. I just know that in regard to memory leaks, turning that option on and then triggering the leak will spit out more information in the logs, so that you(or someone else) can better pinpoint what's causing the leak. If a mod is the cause, then the logs should be pointing to something in the mod's files, and not the vanilla game. 1
Recommended Posts