Search Issue Tracker
Won't Fix
Votes
2
Found in
2018.2.0b6
Issue ID
1045228
Regression
No
MemoryProfiler::UnregisterAllocation crashes when entering to Play mode
To reproduce:
1. Download attached project "VXECS.zip" and open in Unity
2. Open "SampleScene" scene
3. Enter Play mode
Expected Result: Unity Editor successfully enters into the Play mode
Actual Result: Unity Editor crashes
Notes:
- This issue appears both on Windows, OSX, and Standalone builds
- Before crash happens it prints some errors
- The stack traces and errors are shared in the comments section
Reproduced on Unity 2018.1.5f1, 2018.2.0b6 and 2018.2.0b9
Could not reproduce on Unity 2018.3.0a2 because project becomes corrupted
Could not check for regression on 2017.4 because of project needs C# 7.0 or higher version
Comments (2)
-
r-pedra
Oct 01, 2018 13:19
We have this bug really often on 2018.1.7f1, having to launch again Unity around 4-5 times a day.
Sometimes occurs 3-4 times a row.It's really annoying, and we waste a lot of time waiting for unity to launch again. Unity Editor on Mac is really unstable since 2017.
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
- The Up, Down and other Buttons in a Style Sheet's Inspector unselect items when they are clicked while they are disabled
- Virtual Player remains active and still launches when removed from Additional Editor Instances from a custom Play Mode Scenario
- UI Toolkit Editor Window Creator becomes not interactable and greyed out when a long name is entered
- [Web][iOS] Web Player keeps restarting on launch when Native C/C++ Multithreading is enabled
- "Add Scene to Scenes in Build" pop-up reappears after Scene has already been added and another Multiplayer Editor Instance is loaded
Resolution Note:
A crash was caused due to calling UnsafeUtility.Free twice on the same pointer. As the name implies it is unsafe and can cause crashes if used wrong