Search Issue Tracker
Won't Fix
Won't Fix in 6000.1.X
Votes
0
Found in
2021.3.45f1
2022.3.51f1
6000.0.25f1
6000.1.0a2
Issue ID
UUM-86161
Regression
No
Crash on RaiseException when calling maxmath.comb() with the debugger disabled
How to reproduce:
1. Open the attached “IN-87436“ project
2. Make sure the debugger is disabled
3. In the Hierarchy tab, select the "JitCompilationCrashTest" GameObject
4. In the Inspector tab, on the "JitCompilationCrashTest" Component, use the ContextMenu (three dots) and select "Comb Test"
5. Observe the crash
Reproducible with: 2021.3.45f1, 2022.3.51f1, 6000.0.25f1, 6000.1.0a2
Reproduced on: Windows 10 (user), Windows 11
Not reproduced on: No other environment tested
Workaround: Enable the debugger
Note: maxmath.combnotoptimized() does not cause the crash
First few lines of the stack trace:
{noformat}0x00007FFBC874B699 (KERNELBASE) RaiseException
0x00007FFA96930C1C (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\utils\mono-log-common.c:143] mono_log_write_logfile
0x00007FFA9691C822 (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\eglib\goutput.c:172] monoeg_g_logv_nofree
0x00007FFA9691C8FC (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\eglib\goutput.c:217] monoeg_assertion_message
0x00007FFA96C3D6E0 (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\mini\mini-codegen.c:1102] assign_reg {noformat}
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
- Performance Markers Search window shows an empty entry in the list
- Enabling Deep Profiling in Performance Markers Search window breaks Inspector panel buttons when navigating through the marker items
- Dragging selector from selector row background shows preview but does not apply class in UI Builder
- An "InvalidOperationException" error is thrown when TryRemoveItem is used with rebuildTree set to false
- Build fails with IL2CPP error when building on Android platform in a specific project
Resolution Note:
The method in question triggers an excessive amount of inlining. We do not plan on supporting/fixing this case.
Resolution Note (6000.1.X):
The method in question triggers an excessive amount of inlining. We do not plan on supporting/fixing this case.