Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2018.2.0a1
2018.2.0b9
Issue ID
1053208
Regression
Yes
[Memory Profiler] Unity application closes while taking a Memory Snapshot if its scripts' variables take up a lot of memory
How to reproduce:
1. Open the attached Unity project
2. Build and run Windows standalone application
3. Attach profiler to the standalone application
4. Open MemoryProfiler window
5. Press "Take Snapshot" button
Expected result: MemoryProfiler takes a snapshot of the built application; the application is still running
Actual result: The application closes before MemoryProfiler finishes taking its snapshot
Regression first introduced in - 2018.2.0a1
Reproducible with - 2018.2.0a1, 2018.2.0b11, 2018.3.0a3
Not reproducible with - 2017.4.6f1, 2018.1.7f1
Could not test with - 2017.1.0a1, 2017.1.4p2, 2017.2.3p2 (memory snapshot did not inculde scripts' variables)
Notes:
- In the 2018.3.0a3 version of Unity, the application does not close but becomes unresponsive
- Reproducible with both Mac and Windows
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