Video does not play on Acer Chromebook 13 |
|||||
Issue descriptionChromeOS version: 65.0.3325.184, 66.0.3359.181, beta 67.0.3396.55 ChromeOS device model: Acer Chromebook 13 (CB5-311) Case#: 15676424 Description: Video playback is stuck on loading or spinning line when access from a specific Chromebook model - Acer Chromebook 13 (CB5-311) (Big) Steps to reproduce: 1. Open Chrome and go to hegartymaths.com. 2. Click "Watch demo video". 3. The video will just shows loading or spinning line. video of the issue (PII drive link): https://drive.google.com/open?id=1nG4LECHOClHrMpelB_Co21a0sSPXD04E Actual result/Reproduction: The video is stuck and shows it is loading only. It is reproducible on any Acer Chromebook 13 (CB5-311) model running Chrome OS 65 or later. It is reproducible on hegartymaths.com and vimeo.com (which is used as a platform). Not reproducible on other Chromebooks and different video platforms (e.g. youtube.com) Also, issue does not occur when using Ultrasurf Chrome Extension. Expected behavior: The video should play normally. Drive link to logs: https://drive.google.com/open?id=1cKPZbh9hKi_L6UAZ5WyEY64C_tYlx5n0 https://drive.google.com/open?id=1yAB9wmMkglLaeQoM9Xbq0RwCEHngCCAk
,
May 23 2018
,
May 24 2018
Aka, would you perhaps have a moment to take a look please? Thanks!
,
Jun 1 2018
Hi team, customer is requesting for an update on this report. Just let us know if there's any information that you might need for the investigation.
,
Jun 5 2018
Hmm interesting issue. I saw chrome is running with the argument: --ppapi-flash-args=enable_hw_video_decode=0,enable_hw_video_decode_ave=0. So we probably don't use HW decoder when running Flash player. And you mentioned that Ultrasurf can fix this issue. Maybe the root cause is not at video side? Anyway I will try to reproduce the issue and get the further investigation.
,
Jun 5 2018
Hi guys, Update on this case. the issue has been fixed by disabling Harware-accelerated video decode & webRTC H.264 software video encoder/decoder just out of curiosity, why would that be the issue? Thanks for your assistance all the way. Kardo Ameen IT Technician
,
Jun 13 2018
Our customer in comment#8 wants to confirm if what could be the possible reason why the issue has been fixed by disabling Hardware-acceleration. Any insight for this will be very much appreciated. Thank you!
,
Jun 19 2018
akahuang@, any updates with your investigation?
,
Jun 20 2018
Seems like gpu_video_decoder will flush the video before decoding any frame, but V4L2 VDA doesn't handle the flush correctly. I'm checking the issue is at V4L2 VDA side or the driver side.
,
Jul 5
Hi Team, Is there any updates on our investigation? Thanks in advance!
,
Jul 6
It seems the issue is at driver side, but we don't have source code of tegra driver. So maybe I need to do some workaround at VDA or the tegra_v4l2_device wrapper.
,
Jul 6
https://chromium-review.googlesource.com/c/chromium/src/+/1127559 This CL should fix this issue. Now waiting for reviewed and merged
,
Jul 20
Hello Team, Thanks for the last update. Is there any tentative time frame when would be the fix be merged or deploy on the future updates? I appreciate your assistance!
,
Jul 27
re: 14 Chih-Yu, the commit is not merged anywhere yet, even to canary or dev build yet, many people are interest at least tentative time for any merge. Thank you
,
Jul 27
,
Aug 3
Sorry for the late reply. The CL is still reviewing. We expect to merge it soon.
,
Aug 6
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/8bfa58f5c8b533c785a3434b74d55792c31173da commit 8bfa58f5c8b533c785a3434b74d55792c31173da Author: Chih-Yu Huang <akahuang@google.com> Date: Mon Aug 06 06:24:15 2018 v4l2_vda: Skip flush if before any buffer is decoded. When VDA enqueue flush input buffer to the Tegra driver before enqueuing any normal input buffer, Tegra driver will stuck. Now for the devices which do not support V4L2 decoder command, if we call Flush() before decoding any buffer, we skip sending an empty buffer to the driver and notify flush is done. BUG= chromium:845627 TEST=pass video_decode_accelerator_unittest on nyan-big and peach-pit Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel Change-Id: I34a5ec76d95fac8f5bedd3ead08202b1a4e41dcd Reviewed-on: https://chromium-review.googlesource.com/1127559 Commit-Queue: Chih-Yu Huang <akahuang@chromium.org> Reviewed-by: Pawel Osciak <posciak@chromium.org> Cr-Commit-Position: refs/heads/master@{#580811} [modify] https://crrev.com/8bfa58f5c8b533c785a3434b74d55792c31173da/media/gpu/v4l2/v4l2_video_decode_accelerator.cc [modify] https://crrev.com/8bfa58f5c8b533c785a3434b74d55792c31173da/media/gpu/v4l2/v4l2_video_decode_accelerator.h
,
Aug 21
Hi Team, Is there any target Chrome version where the fix will land? A customer would like to know if they need to wait for it a little bit longer or it will coming up soon. Thank you.
,
Aug 27
re: #20 ask them to try on current Dev or Canary (version should be 70.0.3515.0 or higher).
,
Sep 4
The fixed CL (#19) is landed. Close this issue. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by dalecur...@chromium.org
, May 22 2018