Search Issue Tracker
In Progress
Under Consideration for 6000.3.X
Fix In Review for 6000.4.X, 6000.5.X
In Progress in 6000.5.X
Votes
3
Found in
6000.0.44f1
6000.1.0b12
6000.3.0a5
6000.4.0a1
6000.5.0a1
Issue ID
UUM-102308
Regression
No
[macOS] Project fails to load when Virtual Artifacts are Corrupted
How to reproduce:
1. Open the “IN-96978_StuckForever“ project
Expected result: Project opens
Actual result: Project gets stuck while loading
Reproducible with: 2023.1.0a10, 6000.0.44f1, 6000.1.0b12, 6000.2.0a2
Could not test with: 2021.3.50f1, 2022.3.60f1, 2023.1.0a9, 6000.2.0a3, 6000.2.0a7 (The project launches, likely due to the Library folder being rebuilt)
Reproducible on: macOS 15.3.2 (M1 Max)
Not reproducible on: Windows 11
Notes:
- The project gets stuck on “Importing: Initial Asset Database Refresh”
- The project launches if you delete the Library folder
- In the Editor.log multiple errors appear: “The file 'VirtualArtifacts/Primary/f72b49844b3860c49a84722f2a664a39' is corrupted! Remove it and launch unity again!”
- The project launches if you downgrade to 2022.3.60f1 or upgrade to 6000.2.0a7
- After the project is successfully launched, it opens in the original 6000.0.40f1 version as well as other streams.
Comments (1)
-
Dalton-Lima
Oct 15, 2025 11:08
I am having a similar issue in 6000.0.58f2 currently. Here is part of the logs. Currently, it seems we don't have this backported to 6000.0.X (which is the current LTS).
If we clear the build cache it works for a while, but it keeps corrupting like this.
It seems that the SpriteAtlas import tries to read a temp artifact Unity just created, but the file is missing or truncated, which triggers `CachedReader::OutOfBoundsError`.
```
Source Texture (Assets/_Game/Themes/Juicy/Sprites/Navigation/Juicy-NavBarBorder.png) of Sprite (Juicy-NavBarBorder) is using compressed format. To ensure no loss in source pixel details when packing to SpriteAtlas, please use uncompressed format in TextureImporter.
filling image source format : 14, 14, 56, 4 boundary fill : 0
Sprite Atlas Operation : " ## Generate Texture and Render Datas ## " took 0.180178 sec (current mem: 514 MB)
- Packing completed.
Could not open file VirtualArtifacts/Primary/4dc14845c89284557a300bb2e8bceb77 for read
Assertion failed on expression: 'res'
The file 'VirtualArtifacts/Primary/4dc14845c89284557a300bb2e8bceb77' is corrupted! Remove it and launch unity again!
[Position out of bounds!]
Fatal Error! The file 'VirtualArtifacts/Primary/4dc14845c89284557a300bb2e8bceb77' is corrupted! Remove it and launch unity again!
Position out of bounds!
Aborting batchmode due to fatal error
```
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note (fix version 6000.5):
Resolved by adding handling for when fatal errors happens under the preparation phase of the import workers.
Resolution Note (fix version 6000.4):
Fixed by showing users the same error dialog regardless of whether the error occurs in the worker or Editor process. The editor should no longer hang when this error occurs.