Search Issue Tracker
Won't Fix
Votes
1
Found in
2017.3.0f2
Issue ID
978404
Regression
Yes
[Crash] Corrupted "CAB" files in asset bundles causes crash
Reproduction steps:
1. Open "MinimalRepro.zip" project
2. "Portalarium" -> "Build" -> "Character And Resource Asset Bundles"
3. Wait until the bundles finish building and the Editor finishes compiling everything
4. Open "DemoStartupScene" scene
5. Enter Play mode
Expected Result: The scene loads and enter play mode successfully
Actual Result: The Editor crashes with an error: 'CAB' file is corrupted
Reproduced with: 2019.1.0a9, 2018.3.0b10, 2018.2.16f1, 2018.1.9f2, 2018.1.0b4, 2017.3.0p3, 2017.3.0b1, 2017.3.0a7, 2017.3.0a6, 2017.3.0a5
Did not reproduce on: 2017.4.15f1, 2017.3.1p1, 2017.3.0a4, 2017.3.0a1, 2017.2.1p2
Note:
"The file 'MemoryStream' is corrupted! Remove it and launch unity again! [Position out of bounds!]"
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
- Graphics State Collection warm-up does not work when using with Addressables Shaders
- "Baked Shadow Radius" field is visible but inactive when when the Shadow Type is set to "Hard Shadows" under the Light Component
- Crash on OnDemandScheduler::HandleImportWorkerLogs when performing various Unity operations
- Caret is incorrectly offset when naming a file with a lot of characters in the Project window
- Point Cache window displays incorrect title “pCache” instead of full “Point Cache”
Resolution Note:
See edit