Meshes and Textures used on GameObject that has LOD Generator Helper stuck in Ram forever

[Dawid-Game]

Describe the bug
Meshes and Textures used on GameObject that has LOD Generator Helper stuck in Ram forever

To Reproduce
Steps to reproduce the behavior:

1. Put some mesh with material on scene B
2. Use this asset to generate LOD
3. Create scene A which will be main menu
4. Start the game from Scene A and go to scene B
5. Now in your RAM you will see every static mesh for each LOD and for each it is separate instance
6. Now go back to main menu and check again memory. You will see that these meshes and materials (textures) are still in memory
7. If you will play again it will ADD another one to memory instead of using the before one, or release the memory
8. Any kind of code with releasing it its not working

Expected behavior
Release all of this from memory once the scene with it its not loaded

Screenshots

A is the starting the game
B is the returning to the main menu (same scene in A)

This is the texture from other scene. It's impossible to release it from memory

Environment (please complete the following information):

• OS: W11
• Unity Version: 2022.3.35f1

[Whinarn]

@Dawid-Game Thank you for reporting this!

I have tested this a bit on my side, and I can definitely see the possibility of leaks when generating LODs at runtime, but fail to see how it would happen when generating ahead of time in the editor.

From your screenshots, it looks like your mesh renderers are still loaded, which would mean that there are game objects left somehow.

Do you mind creating a small Unity project replicating this problem?
Or if you have the time to debug and potentially create a pull request yourself?

I have not been able to replicate it myself yet, but I've only tested it with Unity 6 yet. I'll see if there's anything different in Unity 2022 when I have some more time to spend.