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
- Volume numeric fields allows adding unlimited number in numeric field which breaks UI, no character limit
- WebGL build dependencies are not refreshed until the Editor is restarted
- “Audio Random Container” allows adding unlimited number in “Audio Clips” numeric field, causing Editor to freeze
- In Deferred rendering path, mixed lights don't render when enabling "Use Rendering Layers" in the Decal renderer feature
- [Windows] Special characters in file names are sorted to the end of the alphabet in the Project window
Add comment