Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.28f1
2022.3.4f1
2023.1.2f1
2023.2.0a22
2023.3.0a3
Issue ID
UUM-42212
Regression
No
Player crashes on "condition `res' not met" when memory is corrupted by a type mismatch
Reproduction steps:
1. Open the attached project "TypeMismatchCrash_2022.zip"
2. Build and Run the project
3. Observe crash
Reproducible with: 2022.3.4f1, 2023.1.2f1, 2023.2.0a22
Could not test with: 2021.3.28f1 (Compiler error)
Reproducible on: macOS 13.4.1 (Intel), Windows 11 (user’s)
Notes:
1. Adding 2021.3.28f1 to the Versions List because the reporter was able to reproduce it with 2021
2. Type mismatch source is specified in the original report
3. Part of the stack trace:
#0 0x007ff813f571f2 in __pthread_kill
#1 0x007ff813eb5b45 in abort
#2 0x0000011c518df5 in monoeg_g_printv
#3 0x0000011c4ff5b1 in mono_dl_fallback_unregister
#4 0x0000011c519157 in monoeg_g_logv
#5 0x0000011c5192bf in monoeg_assertion_message
#6 0x0000011c5192f7 in mono_assertion_message_unreachable
#7 0x0000011c4f4369 in mono_unity_liveness_free_struct
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
- Mouse input is registered incorrectly in Custom RP when downscaling Render Target and rendering Overlay UI before final upscale
- Time.deltaTime is locked to the display's refresh rate when the built Player is moved to a Secondary Display and Windowed Mode is used
- Crash on RaiseException when importing a specific asset
- Crash on RaiseException when opening a specific project
- DownloadHandlerScript.CompleteContent is called twice when building for WebGL
Resolution Note:
There are no fixes planned for this Bug