Audio duration longer than source buffer duration
Reported by
i.kholi...@gmail.com,
Aug 4 2016
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 Example URL: Steps to reproduce the problem: 1. Download the attached html file 2. Open it in Chrome browser 3. And see console log What is the expected behavior? What went wrong? Audio duration longer than source buffer duration Did this work before? N/A Is it a problem with Flash or HTML5? N/A Does this work in other browsers? N/A Chrome version: 52.0.2743.116 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 22.0 r0
,
Aug 5 2016
Tested the issue on windows 7,10, Linux Ubuntu 14.04 and Mac 10.11.6 using chrome version 52.0.2743.116 and canary 54.0.2819.0 with the below steps 1. Opened the attached html on chrome 2.open console,click on play 3.Observed the output as 0.835875. Please find the attached screen cast and confirm anything missed here in triaging the issue.please provide us the expected behaviour to triage the issue further. tried the same on Firefox but got 2 outputs in console( 0.835904, 0.835918). Thanks,
,
Aug 16 2016
Experiencing this is our app as well.
,
Aug 16 2016
kavvaru, in your attached video the audio duration reads as 1.675875, note 0.835875. as noted in your steps to reproduce. In Chrome 52.0.2743.116 and Canary 54.0.2830.0, I get the same results. Chrome reads audio duration as 1.6+. Firefox reads as the correct 0.835904
,
Aug 17 2016
Able to reproduce the issue on windows 7, Linux Ubuntu 14.04 and Mac 10.11.6 using chrome version 52.0.2743.116(Output : 1.675875).It is working fine on canary 54.0.2830.0(output : 0.835875) Please find the reverse bisect information as below Narrow Bisect:: good :: 54.0.2797.0 --(official build 405656) Bad:: 54.0.2794.0 -- (official build 404734) Unable to provide tool bisect as not getting any output after clicking on Run button with invoked chromium builds.?Hecne providing manual CL Change Log:: https://chromium.googlesource.com/chromium/src/+log/54.0.2794.0..54.0.2797.0?pretty=fuller&n=10000 Unable to find the exact suspect from the above CL.Could any one from dev team please look into this issue. Thanks,
,
Aug 17 2016
this issue seems fixed on 54.0.2810.2. kavvaru@, how do we need resolve this bug since it not repro on a newer build?
,
Dec 30 2016
Unable to reproduce the issue on windows 7 using chrome version 55.0.2883.87. Closing this issue as the issue fixed on latest chrome versions. i.kholikov@ Please feel free to raise a new issue if you face any issue on chrome. Thanks, |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ligim...@chromium.org
, Aug 5 2016