Search Issue Tracker
Fixed
Fixed in 2022.3.20f1, 2023.2.13f1, 2023.3.0b10
Votes
0
Found in
2021.3.34f1
2022.3.5f1
2023.2.5f1
2023.3.0b3
Issue ID
UUM-60469
Regression
No
Player crash when loading a content archive of considerable size ~1.6GB
Reproduction steps:
1. Open the attached project “ReproProject”
(the Packages/manifest.json will need to be updated to point to where you extracted the 20200402_V109_VW380_VW382_EXDV_20200127 folder)
2. Copy the folder path of the “Content Archive” package in the project’s manifest.json file
3. Build And Run for Standalone
4. In the “Path” Inputfield in the app, paste the folder location path of the “Contents archive (…/VW380-UPM-Package\20200402_V109_VW380_VW382_EXDV_20200127)” and press the “Load” Button
5. Observe the app’s behaviour
Expected result: A car is loaded from the content archive
Actual result: The app crashes
Reproducible with: 2021.3.34f1, 2022.3.5f1, 2023.2.5f1, 2023.3.0b3
Reproducible on: Windows 10 Pro 22H2
Notes:
- Not reproducible in the Unity Editor
- Could not test the Standalone app built with macOS as the application froze immediately after launch.
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (fix version 2023.3.0b10):
The Editor no longer crashes; however, the error is shown on 2023.X stream is due to bug UUM-64609. This is safe to ignore.
Resolution Note (fix version 2023.2.13f1):
The Editor no longer crashes; however, the error is shown on 2023.X stream is due to bug UUM-64609. This is safe to ignore.