Search Issue Tracker
Fixed
Fixed in 2022.3.60f1
Votes
0
Found in
2022.3.51f1
Issue ID
UUM-84713
Regression
Yes
"Assertion failed on expression" errors thrown in Console when opening Profiler (Standalone Process) window
Steps to reproduce:
1. Create new Unity project
2. Open Profiler (Standalone Process)
3. Obserce the errors thrown in the Console in the Profiler
Actual results: No errors are thrown in the Profiler's Console window
Expected results: Errors are thrown in the Profiler's Console "Assertion failed on expression: 'scriptedImporterClass == SCRIPTING_NULL || uniqueDomainId == MonoDomainGetUniqueId()'"
Reproducible with versions: 2022.3.51f1, 2022.3.57f1
Not reproducible with versions: 2022.3.50f1
Tested on (OS): Ubuntu 20.04, MacBook 2021, Sonoma 14.6 (M1), Windows 11
Notes:
- Errors are clearable, but whenever you reopen Profiler (Standalone Process), they reappear again.
- Issue is not reproducible on macOS Sonoma 14.5 (Intel)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Reflection Probe “Probe Scene Editing Mode:” text is barely visible
- [HDRP] Game view doesn’t refresh after changing Camera Background Type until mouse moves over it
- Some Shaders appear twice in Material Shader selection menu
- Editor freezes with a StackOverflowException when certain asset types are assigned to a managed component in a SubScene via AddComponentObject
- Text Script Importer Reference button links to a Missing Page when clicking the Reference Button in the Inspector
Add comment