Search Issue Tracker
Fixed in 2018.1.X
Votes
0
Found in
2018.1.0a3
Issue ID
967250
Regression
Yes
Profiler leaks memory at a pace of 1-2 MB/s in an empty scene
Reproduction steps:
1. Create a new project.
2. Open profiler and press profile editor. (Works with game profiling as well).
Expected result: Profiler memory usage will not increase or at least it will be very low.
Actual result: Memory usage increases constantly at a pace of 1-2 MB/s.
Reproduced on: 2018.1.0a3.
Works fine on: 2018.1.0a2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment