Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2017.3.0a5
2018.1.0b9
Issue ID
1007815
Regression
Yes
Detailed memory snapshot doesn't produce output when memory is being flooded in Standalone build
To reproduce:
1. Open project attached
2. Make sure Memory Profiler is set to Detailed
3. Build and Run with Memory Profiler attached
4. When Profiling the running build, take a memory sample
Expected: memory snapshot is taken
Actual: snapshot is not being taken
Reproduced in: 2017.3.0a5, 2017.3.1p3, 2018.1.0b10, 2018.2.0a3
Not reproduced in: 2017.1.3p2, 2017.2.2p1, 2017.3.0a4
Note1: snapshot functions as intended when MemoryFlooder script is disabled
Note2: executing the steps in any 2018.2 release crashes the Standalone build
Note3: on some releases, build crashes right away with error in provided picture
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