Search Issue Tracker
Fixed
Votes
0
Found in
5.3.4f1
Issue ID
814206
Regression
No
UnityEngine.Object.Equals incorrectly handles comparisons to a non-UnityEngine.Object derived class
[This happens when the first object is assigned to null]
Steps to reproduce the issue:
1. Open attached project.
2. Open scene named "Default".
3. Enter the play mode.
4. Notice the output of the "Console" window:
foo equals bar: True
bar equals foo: False
List item 0: bar
Actual result:
"object.Equals(objA, objB)" returns true if objA is pointing to null despite the fact that objB is not pointing to null. This might cause unexpected behavior when removing a specific item from the list. Yet, if objA is not pointing to null and objB is pointing to null, the output is correct.
Expected result:
"object.Equals(objA, objB)" should return false if objA is pointing to null and objB is not pointing to null.
Reproduced with:
5.3.2f1, 5.3.5p8, 5.3.6f1, 5.4.0f1, 5.5.0a3.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Add comment