Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2019.4.X, 2020.3.X, 2021.2.X
Votes
0
Found in
2019.4
2020.3
2021.1
2021.2
2022.1
2022.1.0a10
Issue ID
1368301
Regression
No
Crash on MediaEncoder_CUSTOM_Internal_AddFrame_Injected when pushing a frame into MediaEncoder that has been disposed
How to reproduce:
1. Open the attached project from "MediaEncoderCrash.zip"
2. Open Scene "SampleScene"
3. Enter Play Mode and press the spacebar on your keyboard
4. Observe crash
Reproducible with: 2019.4.31f1, 2020.3.20f1, 2021.1.24f1, 2021.2.0b14, 2022.1.0a11
First lines of the stack trace:
0x00007FF6B3A866CF (Unity) MediaEncoder_CUSTOM_Internal_AddFrame_Injected
0x0000019E235EA170 (Mono JIT Code) (wrapper managed-to-native) UnityEditor.Media.MediaEncoder:Internal_AddFrame_Injected (intptr,UnityEngine.Texture2D,UnityEditor.Media.MediaTime&)
0x0000019E235EA013 (Mono JIT Code) UnityEditor.Media.MediaEncoder:Internal_AddFrame (intptr,UnityEngine.Texture2D,UnityEditor.Media.MediaTime)
0x0000019E235E9EDB (Mono JIT Code) UnityEditor.Media.MediaEncoder:AddFrame (UnityEngine.Texture2D)
0x0000019E2278CE03 (Mono JIT Code) [C:\Users\X\Downloads\1368301_MediaEncoderCrash\Assets\MediaEncoderCrash.cs:22] MediaEncoderCrash:Update ()
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
- Errors are thrown after redoing Nested Prefab Variant creation
- Documentation Link does not work when the "VFX Condition" question mark button is clicked
- Documentation Link does not work when the "Spawn State" question mark button is clicked
- Darker lighting in Build when disabling SSAO at runtime
- Animation glitches when using animation layering with base layer transition interruption
Resolution Note (fix version 2022.1):
2022.1.0a16: Added console error in which Editor checks if MediaEncoder is disposed
Resolution Note (fix version 2021.2):
Fixed in 2021.2.6f1
Added Console log "ObjectDisposedException: Cannot access a disposed object."
Resolution Note (fix version 2020.3):
Fixed in 2020.3.27f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.36f1
Error is logged in Console now