Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2019.4.X, 2020.1.X, 2020.2.X
Votes
0
Found in
2019.3.0a9
2019.4
2020.1
2020.1.0f1
2020.2
Issue ID
1268145
Regression
Yes
Crash on WindowsVideoMedia::GetNextVideoFrameGeneric when importing a mov file
How to reproduce:
1. Create a new Unity project
2. Import "crash.MOV"
Reproducible with: 2019.3.0a9, 2019.4.7f1, 2020.1.1f1, 2020.2.0a20
Not reproducible with: 2018.4.26f1
First lines of the stack trace:
0x00007ff72fd08b63 (Unity) WindowsVideoMedia::GetNextVideoFrameGeneric
0x00007ff72fd0874a (Unity) WindowsVideoMedia::GetNextVideoFrame
0x00007ff7308f0908 (Unity) VideoClipTranscode::SetToDefault
0x00007ff7308ef1f9 (Unity) VideoClipTranscode::Import
0x00007ff730c2401f (Unity) VideoClipImporter::GenerateAssetData
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.DrawProceduralIndirect and Graphics.DrawProceduralNow silently dropped on DX12
- [iOS] The safe area value changes when reopening the app in Landscape orientation
- Light flickering when using Forward+ on Mobile
- Crash on mono_g_hash_table_find_slot when entering Play Mode
- [iOS] Crash when pressing "Done" on the keyboard layout
Resolution Note (fix version 2021.1):
Fixed in: 2021.1.0a6
Movies with rotated video (e.g. shot in portrait on a mobile phone) are not supported in Unity. So far, the rotation metadata in the file has simply been disregarded, but recent changes in the VideoPlayer implementation on Windows/UWP caused this metadata to be partially used, leading to out-of-bounds memory access.
Short term workaround is to avoid using such videos in Unity and convert the files prior to import so the rotation is applied (and not just as metadata). The fix being prepared will bring back the existing behaviour of disregarding the rotation metadata. And longer term, when we are ready, we will add full support for rotated videos on all platforms.
Resolution Note (fix version 2020.2):
Fixed in: 2020.2.0b12
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.15f1
Resolution Note (fix version 2019.4):
Fixed in: 2019.4.16f1