Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.1.0f3
Issue ID
966460
Regression
No
Unity crashes on startup at "MemoryProfilerStats::UnregisterObject" when overriding specific virtual method
To reproduce (2017.1.2p3 and 2017.3.0b10):
1. Open attached Unity project "Plugins.zip"
Result: Unity crashes on startup
To reproduce(2017.2.0p2 and 2018.1.0a5)
1. Open attached Unity project "Plugins.zip"
2. Close the project
Result: Unity crashes on closing
Reproduced on: 2017.1.2p3, 2017.2.0p2, 2017.3.0b10, 2018.1.0a5
Note: In BaseNode.cs script, delete "virtual" in line 13 (DrawWindow method) or change it to "abstract" or "override". Now the editor displays multiple errors, but does not crash
Note: In each version the stack trace is a little different, but the cause of the crash is the same:
2017.1.2p3 - (see attached image "2017_1_Crashlog.png")
2017.2.0p2 - (see attached image "2017_2_Crashlog.png")
2017.3.0b10 - (see attached image "2017_3_Crashlog.png")
2018.1.0a5 - (see attached image "2018_1_Crashlog.png")
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (2019.1.X):
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.