New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 805286 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Nov 9
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

webrtc h264 hardware decode failed

Reported by jaychen4...@gmail.com, Jan 24 2018

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36

Steps to reproduce the problem:
1. In WIN 10 open the test demo  https://test.rtc.qq.com:8080/?type=sameaccount&roomid=1900011   in two computer, and one join first, the other join after. 
2. you will found the first frame decode failed, because browser use hw decode default.

What is the expected behavior?
immediately see the picture

What went wrong?
Our product use webrtc to received the video/audio(h264/opus), the video gop is 10s.  
our user mostly use chrome 55, we found that  the first key frame hw decode fail, users need to wait next key fream (10s) and when then browser automatically change to sw decode so that they can see the picture.
users are very hard to close hw decode by chrome://flags/#disable-accelerated-video-decode.
is that any ways to use sw decode default in webrtc, or can we do something in anchor encode to pervent this problems.

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 55.0.2883.87  Channel: stable
OS Version: win10
Flash Version:
 
gpu_2.html
153 KB View Download
首帧慢_360chrome_debug.log
753 KB View Download
and not just in chrome 55 , the browsers below also have the same problem, especially in win 10. 
chrome53.0.2785.104	
chrome63.0.3239.132	
chrome56.0.2924.90	
chrome63.0.3239.84	
chrome55.0.2883.75	
chrome61.0.3163.100	
chrome58.0.3029.110	
chrome61.0.3163.91	
chrome63.0.3239.26	
chrome63.0.3239.108	
chrome62.0.3202.89	
chrome56.0.2924.87	
chrome57.0.2987.133	
chrome62.0.3202.94	
chrome60.0.3112.101	
chrome65.0.3298.4	
chrome60.0.3112.113	
chrome58.0.3029.61	
chrome59.0.3071.115	
chrome53.0.2785.89	
chrome61.0.3163.79	
chrome62.0.3202.62	
chrome57.0.2987.110	
chrome58.0.3029.96	
chrome64.0.3253.3	
chrome59.0.3071.86	
chrome60.0.3112.78	
chrome60.0.3112.20	
Labels: Needs-Milestone
Cc: krajshree@chromium.org
Components: Blink>WebRTC
Labels: Triaged-ET Needs-Feedback
Reporter@ - Could you please upgrade chrome to latest stable #64.0.3282.140 and please check the issue and let us know if the issue still persists or not.

Thanks...!!
Ping!
Components: -Blink>WebRTC Blink>WebRTC>Video
Cc: emir...@chromium.org
Status: WontFix (was: Unconfirmed)
Please reopen if issue still appears in latest Chrome version. Several changes w.r.t. H.264 profile has landed during the year.

Sign in to add a comment