So, I’m trying to track down what is causing/creating a single huge that doesnt change – stays at 161.5 MB no matter what, that I found through memory profiling.
All my research so far points to it being caused by post-processing? The Best Practises page only talks briefly about renderTextures, but elsewhere I’ve seen a lot about having to load and then unload RenderTextures, or else they will stay in memory, but I definitely haven’t been doing any RenderTexture loading.
That TempBuffer is a Temporary Rendertexture rendered at 256x256, probably created by some PostFX (or your Water System?)
Search your codebase for RenderTexture.GetTemporary and check that the created RenderTexture get's cleaned up with RenderTexture.ReleaseTemporary.
That doesnt seem to be the problem, as far as I can tell, though.
I do have a single post-processing effect on my pause screen to do a depth of field blur, but at the point of taking this snapshot that hasn’t been opened, this is only a few seconds in to the first scene.
I know this is a pretty open-ended question but I don’t know where to even start looking to fix this – is it caused by post-processing, or is there something else that creates ?
In my project WITHOUT PostProcessingStack - also exist TempBuffer Screenshot by Lightshot
(1280x720 as screen size of unity on PC)
I mean it doesn’t related to PostProcessingStack, but may be built-in (only this single instance of screen size, not all of RenderTexture.GetTemporary)
Use the frame debugger (scrub through and keep an eye on the Render Target), you’ll most likely spot where that texture comes into play. I don’t have any more answers as I’m dealing with an issue similar to yours right now.
Edit: I think my issue was caused by excessive MSAA
Hi! I am having the same problem. The problem is that those render textures are marked as DontDestroyOnLoad and they depend on the size of the player window.
