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
- Crash on GUIManager::DoGUIEvent when focusing on the Game view window on a specific project
- Asset creation in the Project Browser is not always undone/inconsistent when the undo shortcut is pressed right after creating an asset
- JobTempAlloc memory leak warning is thrown when the Player is shut down
- Graphics State Collection warm-up does not work when using with Addressables Shaders
- "Baked Shadow Radius" field is visible but inactive when when the Shadow Type is set to "Hard Shadows" under the Light Component
Add comment