Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.39f1
2021.3.9f1
2022.1.15f1
2022.2.0b6
2023.1.0a9
Issue ID
UUM-12900
Regression
No
[ChromeOS] "ConsumeOutputBuffers bad buffer index" warning is thrown with video freezing when continuing to play after ~15 seconds of pausing
How to reproduce:
1. Open the user’s attached “VideoPlayerChromebookFreeze” project
2. Build And Run the “SampleScene” Scene on Android
3. Play and Pause the video in Player
4. Wait for ~15 seconds
5. Play the video again
Expected result: Video successfully continues to play
Actual result: Video image freezes with the following output spammed in the Logcat:
”AndroidVideoMedia::VideoDecoder::ConsumeOutputBuffers bad buffer index: -10000”
”sf error code: -38”
Reproducible with: 2020.3.39f1, 2021.3.9f1, 2022.1.15f1, 2022.2.0b6, 2023.1.0a9
Reproducible with devices:
VLNQA00473 - AMD Stoney Ridge Chromebook (grunt), CPU: AMD A4-9120C Radeon R4, GPU: AMD STONEY (DRM 3.42.0, OS: 9
VLNQA00345 - Asus Chromebook CT100PA
Not reproducible with devices:
VLNQA00472 - Samsung Galaxy A52 (SM-A525F), CPU: Snapdragon 720G (SM7125), GPU: Adreno 618, OS: 12
VLNQA00455 - Samsung Galaxy Chromebook (hatch), CPU: -, GPU: virgl (Mesa DRI Intel(R) UHD Graphics (CML GT2)), OS: 11
VLNQA00414 - Galaxy Note10+ 5G (SM-N976V), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 9
VLNQA00409 - Galaxy Z Fold3 5G (SM-F926B), CPU: Snapdragon 888, GPU: Adreno 660, OS: 11
VLNQA00268 - Samsung Galaxy S10+ (SM-G975F), CPU: Exynos 9 9820, GPU: Mali-G76, OS: 10.0.0
Reproduced on: macOS 12.3 (Intel)
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
- [D3D12][XR] SRP Foveation foveated rendering on Windows platform not working when Graphics API is set to D3D12
- The Game view renders extremely saturated or almost black when FSR 1.0, HDR and DX12 are enabled
- Build error on Android when using Patch And Run paired with Play Asset Delivery
- "Browse" button for Xcode in the "Build Profiles" window is too big
- USS styles fail to inherit correctly when contentContainer is overridden in a custom control
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.