Search Issue Tracker
Fixed in 5.6.0
Votes
0
Found in
5.4.2f2
Issue ID
853956
Regression
No
Finalizer causes Unity to crash when entering Play Mode
Reproduction steps:
1. Open project. (Attached by user)
2. Open new scene.
3. Open TestScript.cs.(Assets -> Scripts -> TestScript)
4. Replace code in line 6 with:
public LocalCardDBMS dbms = new LocalCardDBMS();
5. Uncomment 16 and 17 lines.
6. Create new empty GameObject.
7. Attach TestScript to that new GameObject.
8. Press Play.
Expected result: We will enter Play Mode and get some logs in console.
Actual result: Unity crashes.
Issue is caused by LocalCardDBMS.cs (Assets -> Scripts -> Database -> LocalCardDBMS):
~LocalCardDBMS()
{
Disconnect();
}
Reproduced on 5.3.0f4, 5.4.0f3, 5.4.3f1, 5.5.0f1, 5.6.0a3
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
Add comment