Search Issue Tracker
Fixed in 2023.2.5f1
Fixed in 2023.2.X, 2023.3.X, 2023.3.0a12
Votes
0
Found in
2023.1.3f1
2023.2.0a21
2023.3.0a3
Issue ID
UUM-41316
Regression
Yes
Crash on <lambda_8db7f104df3fcd9c943b062f86e208df>::operator() when opening a specific project with a corrupted library
Reproduction steps:
1. Open the attached “ASDQWE” project
Expected result: The project is opened
Actual result: The project crashes while loading
Reproducible with: 2023.1.0a4, 2023.1.3f1, 2023.2.0a21
Not reproducible with: 2021.3.28f1, 2022.3.4f1, 2023.1.0a3
Note: Deleting the Library folder prevents the issue
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
- APV data is sometimes incorrectly loaded from multiple baking sets when loading a scene
- GC Alloc spikes occur when calling UnityEngine.Resolution and UnityEngine.RefreshRate with Equals() and GetHashCode()
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
Resolution Note (fix version 2023.2):
The SourceAssetDB and ArtifactDBs were both corrupted in this user project, and the DBVersion could not be extracted, so we were failing.
A pop up with some options (i.e. recreate DB or Quit) was added to allow users to pick what to do. Batchmode has also been handled, with additional information as to what to do.