Detailed of "Untracked Memory"

Hello,
The information is in the list of Known Limitations:

But the next update is going to bring that information into the window itself, to be shown when the corresponding bar is selected
Also, we are working on closing tracking gaps so the list will get shorter but that will depend on the base Editor version and not the package.

We will update the package documentation accordingly but that will only affect the latest versions of the documentation so the best source for this information is always going to be the documentation for the latest version of the package

 

Also, you have a snapshot there that suffers from a bug in the managed crawler in the package, which is why the Managed Object memory size is Unknown. That should be fixed with the next update.

That also likely explains why System.Object is claiming to take up 3 GB
If the next update does not fix this, please report a bug. We only need the snapshot to reproduce this, no project

 

Actually... The bugs I fixed were around string memory parsing causing some overflow. I'm not certain that the issue seen in your screenshot is fixed with that.

Could you please file a bug report via the Editor's menu bar: Help > Report a Bug?
I don't need the project, just the snapshot and the Issue ID that you should get from the response email.
With that I can make sure this is fixed asap, either with the next release or a quick follow up release.

 

The update, 0.5.0-preview.1, which is now released just brings the description to the UI.

Reducing this category by filling the blank spaces with info will happen gradually and with updates to the base Unity Editor and Player, not via a package update.

Getting data for IL2CPP Virtual Machine memory is in the works for 2022.2. I'm unsure if that will be backported.

Allowing Plugins to register their memory via Unity's Memory manager is in the works too. Once that's implemented, it will depend on plug-in creators to actually use that API or their memory will remain untracked.

Size of DLLs for all platforms is also in the works.

Until this work is done and shipped, the only thing you can do to see more about these is to use native platform specific profilers.

 

Every allocation made with Unity's allocators is practically per definition tracked. So this would show up under other. It should be listed in a bit more detail in the All Of Memory tables in the 1.0 version, but for temp memory I think it only shows the Temp Allocator size.

 

That's the Unity Objects Breakdown which is a filtered view showing only the memory used for types inheriting from UnityEngine.Object.

You can open the Objects and Allocations page or load that snapshot into the memory Profiler in an empty project using Unity 2022.2 and the 1.0 of the package and explore the All Off Memory page to see all of that memory usage.

Also there are ongoing efforts to reduce the impact of shader variants and having an explosion of shader variants duplicated into memory when shaders are included in multiple Asset Bundles. There's other threads in the forums with details and updates on that.

 

Just to add on this note - RenderTextures should be properly tracked as of 2023.1.0b6 and 2023.2.0a3, with the exception of Vulkan MSAA RTs (landed in 2023.2.0a6 and coming to 23.1 soon)

 

It'll vary depending on platform, API etc... but, hopefully you shouldn't have to worry about it: We backported the RT fixes to 2022.2.16f1, which, given how close a version you're on, should be an easy upgrade! Or at the very least, worth trying just to see how memory compares.