Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2018.3.X
Votes
3
Found in
2018.2.0a2
2018.2.0a4
Issue ID
1012884
Regression
No
[Memory Profiler] Unity Editor crashes when taking a Snapshot
To reproduce:
1. Download attached project "1011626.zip" and open in Unity
2. Enter the Play mode
3. Open the Memory Profiler window and press the "Take Snapshot" button
Expected Result: Unity Editor successfully takes a Snapshot
Actual Result: Unity Editor crashes
Notes:
- In some cases (e.g. 2018.2.0a7 version), the crash occurs after taking more than two or three screenshots when a project is opened again crash occurs after the first try to take a screenshot
- The stack traces are shared in the comments section
- This issue occurs on both Windows and OSX
- In Unity 2018.2.0a2, 2018.2.0a3 and 2018.2.0a4 Stack traces are different
Reproduced on Unity 2018.2.0a2, 2018.2.13f1, 2018.3.0a1, 2018.3.0b4 (ca760a), 2019.1.0a1, 2019.1.0a6
Not reproduced on Unity 2017.4.13f1, 2018.1.9f1, 2018.2.0a1, 2018.3.0b4 (44012b), 2018.3.0b7
Regression on Unity 2018.2.0a2 and 2019.1.0a1
Comments (2)
-
RobPixelToys
Dec 07, 2018 13:53
Reproduced on Unity 2017.4.13f1 (OSX) - crash occurs consistently if used during play mode.
Add comment
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
- Package signature validation unexpectedly return an invalid signature status if the validation check is done after the code signing certificate validaty range has passed
- 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
Resolution Note (fix version 2019.1):
Fixed on .NET 4.x
Resolution Note (fix version 2018.3):
Fixed in 2018.3.4f1