Search Issue Tracker
Fixed in 2018.4.X
Fixed in 2017.4.X, 2019.2.X
Votes
0
Found in
2018.3.0a1
2018.3.7f1
2019.1.0a1
2019.2.0a1
Issue ID
1135251
Regression
No
[Crash] AssetBundleLoadFromAsyncOperation::GetAssetBundleBlocking when loading MANY AssetBundles via LoadFromStreamAsync
How to reproduce:
1. Open the "AssetBundle_Crash.zip" project
2. Open the "SampleScene.unity" scene
3. Press Play
4. If Unity didn't crash in 10 seconds, exit Play mode and repeat from step 3
Actual result: Unity crashes.
Reproducible with: 2018.2.0a9, 2019.1.0b8, 2018.3.10f1, 2018.1.9f2.
From the user:
LoadFromStreamAsync Crashes when loading many bundles simultaneously
1. What happened
When attempting to load many bundles simultaneously (over 10) using LoadFromStreamAsync, Unity crashes
2. How we can reproduce it using the example you attached
* Open the Scene named SampleScene
* Highlight the SceneManager GameObject in the Hierarchy and unsure that 'Load Flats' is checked and 'Flats to Queue Simultaneously' is over 10
* Press Play
* If crash does not occur, try a higher number
-------------------------------------------
Fixed in 2019.3.0a5, 2019.2.0b10, 2018.4.10f1.
Comments (2)
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
- ACES Tonemapping causes banding artifacts and negative values in ColorGradingLUT when HDR is enabled and "High Dynamic Range" Grading mode is selected while Android Platform is used
- Android Player freezes when an Audio Source is playing and an incoming call is picked up and then hung up and the Audio Source is started again
- Green success icon is poorly visible in the light Unity theme
- Incorrect input into the Input Field when using Microsoft IME Japanese
- Multiplayer role "ClientAndServer" is displayed without the spaces in the "Play Mode Scenarios" window
Animallica
Oct 01, 2019 22:38
I need this fixed for 2017.4, the 2017.4 LTS support didn't end, I hope it will be fixed for this version as well.
EthanFischerICS
Sep 16, 2019 16:48
Is this fix still planned for 2018.4?