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
- The Property's reference does not default to "_MainTex" when creating a new Texture2D Property in a ShaderGraph
- The "--additional-libraries" argument is ignored when building projects with the IL2CPP scripting backend
- Matching Selectors list not updating correctly with element's pseudo-state updates
- [Android] Crash on vendor/lib64/egl/libGLES_mali.so when Graphics Jobs(Experimental) is disabled and the Player is running on the Google Pixel 6 with the March security patch installed
- Profiler does not profile after building the Project with Autoconnect Profiler Option enabled
Add comment