Search Issue Tracker
Fixed in 2022.3.9f1
Fixed in 2022.3.X, 2023.1.X, 2023.2.X, 2023.3.X, 2023.3.0a3
Votes
0
Found in
2022.3.6f1
2023.1.6f1
2023.2.0b2
2023.3.0a1
Issue ID
UUM-44046
Regression
Yes
Projects are not opening due to an Infinite Loop when a Script with the OnPreprocessAsset() Function from the Documentation is present
How to reproduce:
1. Open the user-attached “AddressablesShaders.zip” Project
Expected result: The Project opens
Actual result: The Unity Editor becomes unresponsive and the Project doesn’t open
Reproducible with: 2022.2.0a3, 2022.3.6f1, 2023.1.6f1, 2023.2.0b2
Not reproducible with: 2021.3.29f1, 2022.2.0a2
Reproduced on: macOS Ventura 13.4 (Intel)
Notes:
- Issue is not reproducible when the Project has Compilation Errors
- The Function causes an Infinity Loop in the Script Compilation process
- “OnPreprocessAsset()” Function is taken from this documentation: [https://docs.unity3d.com/2022.3/Documentation/Manual/DefaultPresetsByFolder.html]
- Workaround is to not process folders in the Function
- If the issue no longer reproduces on the Reproducible versions, delete the Library folder
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
- The sidebar reopens when Unity Hub is started when Unity Hub was closed with the sidebar closed
- Characters are invisible in the TextField when certain Japanese characters are used
- "InvalidOperationException" is thrown when using Prefab > Replace to replace a Canvas GameObject with a Prefab that has an incompatible root Transform type
- Looping AudioSource resumes from the wrong playback position when the app is backgrounded and resumed on iOS Safari
- "AnyState Transition Created" action can be undone when pressing "Auto Generate Animation" on the uGUI GameObjects
Resolution Note (fix version 2023.3):
Issue stems from faulty code in the documentation, it was updated with the code that does not have the issue.
Resolution Note (fix version 2023.2):
Issue stems from faulty code in the documentation, it was updated with the code that does not have the issue.
Resolution Note (fix version 2023.1):
Issue stems from faulty code in the documentation, it was updated with the code that does not have the issue.
Resolution Note (fix version 2022.3):
Issue stems from faulty code in the documentation, it was updated with the code that does not have the issue.