Search Issue Tracker
Fixed in 2019.2.X
Duplicate in 2018.3.X, 2019.1.X
Votes
1
Found in
2018.2.8f1
Issue ID
1111132
Regression
Yes
Memory Leak is present in profiler's GfxDriver section
To reproduce:
1. Open the last attached project (case_1111132-NoParticlesMemoryLeak (1).zip (692.1 KB), by RichardK)
2. Build a player
3. Start the player and attach the profiler
4. Observe the memory in the Profiler
Expected: no memory leakage
Actual: GfxDriver is leaking memory (leaks every ~15 seconds, 4-10 mb)
Reproduced in: 2018.2.20f1, 2018.3.1f1, 2019.1.0a13, 2019.2.0a4
Notes:
- Tested on Win
- issue was originally presumed particle-related, but after removing all particles it still occurs
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment