Search Issue Tracker

Fixed

Fixed in 2020.3.48f1, 2021.3.24f1, 2022.2.17f1, 2023.1.0f1, 2023.2.0a11

Votes

36

Found in

2020.3.46f1

2021.3.16f1

2022.1.24f1

2022.2.11f1

2023.1.0b8

2023.2.0a1

Issue ID

UUM-21948

Regression

Yes

Crash on WindowsVideoMedia::GetFirstReadyTextureTime when focusing GameObject in Tutorial

--

-

How to reproduce:
1. Open and create project with the "2D Platformer Microgame" sample
2. Enter and continue with the ""Change Color" Tutorial
3. When prompted, select "Player" in the Hierarchy and click and hold "F" on your keyboard for about 10 seconds

Reproducible with: 2021.3.16f1
Not reproducible with: 2020.3.43f1, 2021.3.15f1
Couldn't test with: 2022.1.24f1, 2022.2.2f1, 2023.1.0a25 (No template to test with)

Tested on: Windows 11

Note: Issue reproduces around half of the time, sometimes crashes without stack trace

First lines of the stack trace:
0x00007ff67eb1a591 (Unity) WindowsVideoMedia::GetFirstReadyTextureTime
0x00007ff67fb125c6 (Unity) VideoMediaTextureOutput::ConsumeFrame
0x00007ff67eb02ec5 (Unity) VideoClipPlayback::GetTextureAtTimeInternal
0x00007ff67eb08f31 (Unity) VideoPlayback::GetTexture
0x00007ff67eaff17d (Unity) VideoPlayer::VideoUpdate
0x00007ff67eafefce (Unity) VideoManager::VideoUpdate

  1. Resolution Note (fix version 2023.2.0a11):

    Serialized access to thread-unsafe texture containers used from multiple threads when handling looping during playback.

  2. Resolution Note (fix version 2023.1.0f1):

    Serialized access to thread-unsafe texture containers used from multiple threads when handling looping during playback.

  3. Resolution Note (fix version 2022.2.17f1):

    Fixed Serialized access to thread-unsafe texture containers used from multiple threads when handling looping during playback.

  4. Resolution Note (fix version 2021.3.24f1):

    Fixed Serialized access to thread-unsafe texture containers used from multiple threads when handling looping during playback.

  5. Resolution Note (fix version 2020.3.48f1):

    Fixed serialized access to thread-unsafe texture containers used from multiple threads when handling looping during playback.

Log in to vote on this issue

Comments (8)

  1. liu1067082341

    May 25, 2023 02:50

    Untiy, the greatest bug producer

  2. Erveon

    Apr 07, 2023 21:22

    One day, Unity will release an LTS update that introduces less bugs than it fixes. Today is not that day.

  3. kimxslay

    Apr 06, 2023 09:45

    Please fix it, it's so not salami.

  4. Vdash

    Apr 06, 2023 09:29

    Please fix it soon

  5. Immu

    Apr 05, 2023 23:48

    I started to saw this error when upgrading from 2020.3.42 to 2020.3.43, which was very sad for a LTS x)
    Can't wait to see it fixed.

  6. galacticnanocyte

    Apr 05, 2023 21:48

    Hoping this issue gets fixed soon :)

  7. tntfoz

    Mar 17, 2023 11:41

    Hi, can you please look at fixing this for the 2020 LTS branch (which I know is due to end soon) however this problem has been a showstopper since the 2020.3.43 release (we're currently up to 2020.3.46).

    Basically all fixes and improvements to the 2020 LTS branch since 3.43 have essentially been wasted if this bug remains present.

  8. HoldTheLine

    Mar 16, 2023 22:05

    Nice! I'm glad to see some movement on this. We'll keep our fingers crossed for that 2021.3 fix, as the error is keeping our team from upgrading to the latest LTS.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.

Latest issues

See all new issues