Search Issue Tracker
Fixed
Fixed in 2021.3.29f1, 2022.3.2f1, 2023.1.0b19, 2023.2.0a15
Votes
0
Found in
2021.3.11f1
2022.1.19f1
2022.2.0b9
2023.1.0a13
2023.2.0a1
Issue ID
UUM-16390
Regression
No
Crash on CachedWriter::Write when building AssetBundle (.byte file >2GB)
Reproduction steps:
1. Open the user’s attached project
2. Click “Assets/Video/sample.bytes”
3. In the Inspector Window, under the “Asset Labels”, click the “AssetBundle” dropdown
4. In the dropdown, select “New…” and enter any name
5. Click Build > “Asset Bundles”
Expected result: AssetBundle is created from the .bytes file
Actual result: Unity Editor crashes
Reproducible with: 2021.2.0a17, 2021.3.11f1, 2022.1.19f1, 2022.2.0b9, 2023.1.0a13
Couldn’t test with: 2020.3.40f1, 2021.2.0a16 (crashed when clicking “Assets/Videos/sample.bytes” because of Size overflow in allocator)
Reproducible on: Window 11 Pro 21H2
First lines of the stack trace:
{noformat}0x00007ff7202e5033 (Unity) CachedWriter::Write
0x00007ff7205a9df2 (Unity) TextAsset::Transfer<StreamedBinaryWrite>
0x00007ff720679e47 (Unity) SerializedFile::WriteObject
0x00007ff720664279 (Unity) PersistentManager::WriteFile
0x00007ff720665e5f (Unity) PersistentManager::WriteFile{noformat}
Note: Reimport project on every version change
Note: This is caused because the Videos/sample.byte file is more than 2GB. Unity does not support more than 2GB in the serialization of a single object and content of a .byte file will be stored as an embedded object inside the AssetBundle. Such a large object is almost certainly not going to be efficient, even if we did support such a large size. When fixing this ticket we would aim to add an error message and build failure in this case, rather than letting the Editor crash.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Missing Render Feature "Full Screen Pass Render Feature" in any “Universal Renderer Data” asset when upgrading from 2022.3
- Inconsistent ParticleSystemVertexStream.PercentageAlongTrail data range in Trail Texture Modes except "Stretch"
- The Graph Debug Window can be right clicked through and the Node Workspace is manipulated instead
- [Linux] Top left corner of the screen is unresponsive when the Editor recompiles
- [Android] [Vulkan] Cubes stuck on the first few frames of rotation and application flickering when an Overlay Camera is added to the Camera Stack with MSAA enabled
Add comment