Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2018.4.X, 2019.2.X
Votes
0
Found in
2019.3.0a2
2019.3.0a6
Issue ID
1162426
Regression
Yes
[Android] [VideoPlayer] When one makes a seek to a non-zero frame and then immediately a seek to 0, Video freezes for a while
How to reproduce:
1. Open the attached project
2. Build and run WebmSync scene on Android device
3. When video starts playing Press Forward button few times (also you can switch to another video, one is mp4 another one webm)
4. Then press Backward button 5 times quickly
Result: Video freezes for ~6 seconds and then continues playing
When one makes a seek to a non-zero frame (e.g. 475) and then a seek to 0 immediately without waiting for the seek to complete. Internally, we think the seek has already completed (because the seek to 475 has not yet been completed by pulling one frame) and we optimize it out. What this means is that the media stays at 475 while waiting for the VideoPlayer to be at 476 and that is why video freezes for some time.
Reproducible: 2019.3.0a6, 2019.3.0a2
Not reproducible: 2019.2.0a11, 2019.2.0b6, 2019.3.0a1
Tested and reproduced on:
VLNQA00279, SAMSUNG GALAXY S10+ (SM-G975U), Snapdragon 855 (SM8150), Adreno (TM) 640, 9.0.0
VLNQA00166, HUAWEI P20 PRO (EML-L29), P20 PRO (EML-L29), Mali-G72, 8.1.0
VLNQA00024, XIAOMI MI 5 (MI 5), Snapdragon 820(MSM8996), Adreno (TM) 530, 7.0.0
VLNQA00093, SAMSUNG GALAXY S6 EDGE (SM-G925F), Exynos 7 Octa (7420), Mali-T760, 7.0.0
VLNQA00036, MOTOROLA MOTO G GOOGLE PLAY EDITION (XT1032), Snapdrago 400, Adreno 305, 5.1.0
Tested and didn't reproduce on:
iPhone XS iOS 12.3.1
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note (fix version 2019.3):
Better logic to distinguish between seek to 0 and seek to current position in contexts where the current position is not yet established.