Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.34f1
2022.3.17f1
2023.2.5f1
2023.3.0b2
6000.0.0b11
Issue ID
UUM-60015
Regression
No
The Player instant crashes when Building And Running a project with RuntimeInitializeLoadType.AfterAssembliesLoaded implementation
Reproduction steps:
1. Open the attached “repro-project“
2. File > Build And Run
3. Observe the Player crashing
Reproducible with: 2021.3.34f1, 2022.3.17f1, 2023.2.5f1, 2023.3.0b2
Reproduced on: Windows 10
Not reproducible on: No other environment tested
Notes:
1. Reproducible both with Mono and IL2CPP Scripting Backends
2. This crash does not produce debuggable information, such as a crash dump, and no Player log is generated
3. The issue is identified as being caused by the use of RuntimeInitializeLoadType.AfterAssembliesLoaded in the Unity project. This setting schedules the execution of a method after all assemblies are loaded but before the scene is loaded
4. As a workaround, switching the RuntimeInitializeLoadType from AfterAssembliesLoaded to BeforeSceneLoad prevents the crash
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
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
- White lighting artifact when a point light with a small emission range and "Hard Shadows" touches an object while a directional light with "Soft Shadows" and another point light are present
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.