Search Issue Tracker
Active
Under Consideration for 6000.0.X, 6000.1.X, 6000.2.X, 6000.3.X
Votes
0
Found in
6000.0.54f1
6000.1.12f1
6000.2.0b10
6000.3.0a2
Issue ID
UUM-111886
Regression
No
Crash on WindowsVideoMedia::GetVideoFrameAtIndex when importing a specific MP4 file
How to reproduce:
1. Open the attached “IN-105201.zip” project
2. Reimport “Assets/crash.mp4”
3. Observe the crash
Reproducible in: 2023.1.0a1, 6000.0.54f1, 6000.1.12f1, 6000.2.0b10, 6000.3.0a2
Reproducible on: Windows 11
Not reproducible on: MacOS 15.5 Sequoia (Intel)
Note: If the Editor does not crash on first reimport, reimport the file again
First few lines of stacktrace:
{noformat}0x00007FFDB3E3DDC3 (Unity) WindowsVideoMedia::GetVideoFrameAtIndex
0x00007FFDB4761447 (Unity) VideoClipTranscode::SetToDefault
0x00007FFDB475F426 (Unity) VideoClipTranscode::Import
0x00007FFDB49981C4 (Unity) VideoClipImporter::GenerateAssetData
0x00007FFDB490B9CE (Unity) ImportToObjects{noformat}
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- TSS Inspector creates invalid Project Relative paths for USS references in packages when adding References via Inspector
- Screen Space Ambient Occlusion is not visible when the directional light intensity is 0.001 or lower with the Deferred Rendering Path selected
- Unlinking Unity project from cloud throws "DirectoryNotFoundException" errors when the Build Automation package is installed
- Numeric input field for “Prewarm Time” doesn’t fully display decimal values
- Sprite Editor Overlay Menu issues
Add comment