Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2019.1.X
Votes
1
Found in
2018.2.20f1
2018.3.0a1
2019.1.0a1
2019.2.0a1
Issue ID
1118331
Regression
Yes
When building a lot of AssetBundles some Bundles will result in corrupted resources ".resources" or ".resS" will be 0 bytes
Reproduction steps:
1. Open "1118331.zip" project
2. "Generate" -> "1000"
3. Open Asset Bundle Browser Window
4. Build Asset Bundles
5. Open Asset Bundle Output Path
6. Sort by size, from smallest to biggest
7. Extract the First AssetBundle with "WebExtract"
Expected Result: WebExtract finishes successfully
Actual Result: WebExtract hangs, due to corrupt Asset Bundle
Fixed in: 2019.2.0a5, 2019.1.0b4, 2018.3.6f1
Reproduced with: 2019.2.0a2, 2019.1.0a14, 2018.3.3f1, 2018.2.20f1
Did not reproduce on: 2017.4.19f1
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
- Crash with multiple stack traces when playing video on a render texture with low-end graphics devices
- Circle handle of the Game view scale slider bar disappears when the scale is set to 1x
- Asset Bundles non-deterministic behavior with CRCs and hash when a video has Transcoding enabled and Sprite Atlas has an override option enabled
- [Quality Hackweek] Errors "InvalidOperationException: EnsureRunningOnMainThread can only be called from the main thread" and "NullReferenceException" shown when switching build platforms with Muse Texture package installed
- "Importer(DefaultImporter) generated inconsistent result for asset" warnings are thrown when reimporting the "URP" texture
Resolution Note (fix version 2019.1):
backported