Search Issue Tracker
Fixed
Fixed in 2022.3.9f1, 2023.1.11f1, 2023.2.0b7, 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
- Prefab Override popup displays on wrong monitor when Inspector width is resized to minimum
- Scroll View is not moving by inertia after scrolling by click and dragging when Editor window is minimized and Canvas "Render Mode" is set to "World Space"
- "type mismatch error" occurs when the currentDirectionWS output of a Sample Water Surface node is connected to a float3 input
- URP Material Upgrade utility does not enable Alpha Clipping when material had Rendering Mode set to Cutout
- Particle System emission ignores the Sprite Atlas when using a Material that has the "Include in Build" setting unchecked
Resolution Note (fix version 2023.3.0a3):
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.0b7):
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.11f1):
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.9f1):
Issue stems from faulty code in the documentation, it was updated with the code that does not have the issue.