Search Issue Tracker
Not Reproducible
Votes
0
Found in
2020.3.46f1
2021.3.20f1
2022.2.10f1
2023.1.0b7
2023.2.0a5
2023.3.0a3
6000.0.0b11
6000.1.0a7
6000.2.0a1
Issue ID
UUM-29659
Regression
No
"Assertion failed on expression: 'm_ProducerThreadId == CurrentThread::GetID()'" is thrown when VideoPlayer loops several times in the Build
How to reproduce:
- Open the attached project "VideoCrashNoHL2.zip"
- Build the project for UWP
- Open the built solution in Visual Studio
- Start Debugging on Local Machine
- Wait for the video to loop several times
Expected results: No errors thrown
Actual results: "Assertion failed on expression: 'm_ProducerThreadId == CurrentThread::GetID()'" is thrown
Reproducible with: 2020.3.46f1, 2021.3.20f1, 2022.2.10f1, 2023.1.0b7, 2023.2.0a5
Not reproducible with: 2022.3.61f1, 6000.0.46f1, 6000.1.0b14, 60002.0a9
Reproducible on: Windows 10
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note:
Thank you for reporting a bug to Unity.
This issue has been fixed in an upcoming release. We have reviewed the issue carefully, and in this case, the team is unable to prioritize backporting this bug to existing releases. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that a backport may destabilize a release in production.
Today we will be closing this issue. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note:
Thank you for reporting a bug to Unity.
This issue has been fixed in an upcoming release. We have reviewed the issue carefully, and in this case, the team is unable to prioritize backporting this bug to existing releases. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that a backport may destabilize a release in production.
Today we will be closing this issue. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.