Search Issue Tracker
By Design
Votes
0
Found in
2020.3
2020.3.25f1
2021.2
2022.1
2022.2
Issue ID
1399602
Regression
No
Crash on entering Play Mode when '==' and '!=' operators are overridden
Reproduction steps:
1. Open the user's attached project
2. Open the '03 - GameplayScene' Scene
3. Enter Play Mode and observe a crash
Reproducible with: 2020.3.30f1, 2021.2.13f1, 2022.1.0b9, 2022.2.0a6
Could not test with: 2019.4.35f1 (due to compile errors)
Notes:
- Commenting '==' and '!=' operators overrides in the 'ItemFillColor.cs' script fixes the issue
- No stack trace is obtained and Bug Reporter doesn't launch after the crash
- Before the crash, a warning 'DontDestroyOnLoad only works for root GameObjects or components on root GameObjects. UnityEngine.StackTraceUtility:ExtractStackTrace ()' appears in the Console
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
- [URP][XR] Spotlight shadows flicker when Deffered Rendering Path is selected and rotating the HDM view in XR
- Scene view audio toggle doesn't work after disabling and enabling audio source component with audio random container
- Pitch changes while paused messes up scheduling of the audio random container
- Crash on detail::ComputeShaderSnippetKey when entering the Play mode
- Unable to interact with Material Inspector window when creating a new Material and renaming it
Resolution Note:
There is an infinite recursion in the == operator implementation leading to a StackOverflow (a == null match the operator and thus call itself recursively)