Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2019.4.X, 2020.3.X, 2021.1.X
Votes
1
Found in
2019.4
2019.4.16f1
2020.2
2021.1
2021.2
Issue ID
1306061
Regression
No
[Accelerator] The Editor crashes when downloading corrupted Metadata files from the Accelerator cache database
How to reproduce:
1. Install Unity Accelerator
2. Create and open a new project
3. Open the Preferences window from Edit > Preferences
4. Open the Cache Server tab and Insert the Accelerator address that was provided after the 1st step
5. Close the project
6. Delete the Library folder of the project created in the 2nd step
7. Open and close the project
8. Navigate to the Accelerator storage location and open the "cachedb" folder
9. Find and open a Metadata file in the hashed folders
10. Remove a byte from the file and save it
11. Open the project
Expected results: the cache corruption is detected and the faulty files are skipped without crashing
Actual results: the Editor crashes
Reproducible with: 2019.4.19f1, 2020.2.2f1, 2021.1.0b4, 2021.2.0a3
Could not test with: 2018.4.30f1 (Unity Accelerator not available)
Notes:
-The Editor always crashes while downloading Metadata files but never while downloading Artifact files
-The crash stack trace isn't always consistent and depends on where the corruption was introduced in the 10th step
- Corrupting non-Metadata files in the "cachedb" folder causes other types of issues (usually not crashes), most often warnings that the Editor failed to deallocate some memory
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0a7
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.2f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.23f1