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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment