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
- Character spacing value is not applied when using a specific font asset
- [Android][IL2CPP] Player crashes on __memcpy_aarch64_simd+276 when invoking native code via a plugin on some ARM64 Android devices
- [Android]Resources fail to load when the AAB build contains a large Addressables Bundle
- Unity is loading internal version of SharpZipLib instead of local version
- The Context Menu items are ordered incorrectly
Add comment