Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Duplicate in 2019.4.X
Votes
0
Found in
2019.2.5f1
2019.3
2019.3.0f1
2020.1
Issue ID
1202385
Regression
Yes
Unity crashes when VideoPlayer component attempts to play VideoClip loaded through AssetBundle.LoadFromStream()
Steps to reproduce:
1. Open the attached project (case_1202385-StreamVideoBugReport.zip)
2. Enter Play Mode
3. Click the "Load" button
Expected result: Video plays
Actual result: Video does not play and Unity crashes
Reproduced in: 2019.2.5f1, 2019.2.16f1, 2019.3.0f2, 2020.1.0a15
Not reproducible in: 2017.4.35f1, 2018.4.14f1, 2019.2.4f1
Note: In Unity versions 2019.2.0b5 to 2019.2.4f1 (earlier 2019.2 versions unchecked), instead of crashing, the following is outputted to the console:
WindowsVideoMedia error 0x8007007b while reading archive:/CAB-f4056db44bc36994fffbc89e2912fee2/CAB-f4056db44bc36994fffbc89e2912fee2.resource
Context: MFCreateFile
Error details: The filename, directory name, or volume label syntax is incorrect.
Similar issue regarding the error (fixed in 2019.3): https://issuetracker.unity3d.com/issues/windowsvideomedia-error-0x8007007b-is-thrown-when-importing-an-assetbundle-with-video-in-it
-
kraihd
Dec 13, 2019 02:42
It derives not only WindowsVideoMedia.
Even some platforms where non-filesystem-entry video streaming is available (ex. iOS, Android) have same problem.
It will be fixed only after they can play from AssetBundles from Stream.
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
- A vertical graphical artifact appears on Android Player when clearing Z & Stencil Buffer and running with OpenGLES3 Graphics API
- Player crashes when built with IL2CPP Scripting backend
- TextMeshPro package throws multiple Shader errors when importing TMP Essential Resources
- Package Manager search text field has no validation and leads to Editor freezes
- PlayerLoop.SetPlayerLoop() function is ignored when playing game in Player
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0a17
Logic wasn't ready to try to translate a managed stream into a local filesystem entry. The operation cannot be performed since the path is hidden, but the operation now only properly reports failure instead of crashing during the test.
Resolution Note (fix version 2019.3):
Fixed in 2019.3.0f4
Logic wasn't ready to try to translate a managed stream into a local filesystem entry. The operation cannot be performed since the path is hidden, but the operation now only properly reports failure instead of crashing during the test.