Search Issue Tracker
Fixed in 2022.2.19f1
Fixed in 2022.2.X, 2023.1.X, 2023.2.X, 2023.2.0a17
Votes
0
Found in
2022.2.13f1
2023.1.0b10
2023.2.0a8
Issue ID
UUM-31318
Regression
Yes
Crash on MonoScriptInfoScraper::GetAssemblyScrapedMonoScripts when opening the project containing com.unity.netcode.gameobjects
Reproduction steps:
1. Open the attached Project “OpenCrash”
Expected result: The project opens
Actual result: Editor crashes
Reproducible with: 2022.2.0a3, 2022.2.13f1, 2023.1.0b10, 2023.2.0a8
Not reproducible with: 2020.3.46f1, 2021.3.22f1, 2022.2.0a2
Reproducible on: macOS 13.2.1 (M1 Max), Windows 10
First few lines of stack trace:
0x00007FFFA5F91817 (Unity) MonoScriptInfoScraper::GetAssemblyScrapedMonoScripts
0x00007FFFA5F99662 (Unity) MonoScriptInfoScraper::ScanForSourceGeneratedMonoScriptInfo
0x00007FFFA5FBD9D6 (Unity) MonoManager::AnalyzeDomain
0x00007FFFA5FC6D3F (Unity) MonoManager::LoadAllAssembliesAndSetupDomain
0x00007FFFA5FC9CEF (Unity) MonoManager::ReloadAssembly
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "No HDR monitor detected." warning is shown in the Rendering Debugger even when the Editor is on HDR-enabled monitor
- Shader Graph Enum Keyword Default Value changes after reordering Entries
- Light Explorer throws “ArgumentException” error when disabling all columns from the Multi-column panel context menu
- "Freeze Camera For Culling" options are inconsistent between the Game view overlay and Rendering Debugger window
- Crash on GetOriginalSourceOrVariantRoot when creating a scene from a specific template
Add comment