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
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- “ArgumentOutOfRangeException” after saving, reseting and re-add Default Tile Palette Tools to the list in Preferences window
Add comment