Audio codec crashes after playing media for some time
Reported by
epoplavs...@2point0concepts.com,
Jul 8 2016
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2790.0 Safari/537.36 Platform: 8172.60.0 (Official build) stable-channel Example URL: Steps to reproduce the problem: 1. Open this video in chromeOS browser 2. Add "loop" attribute to the video html element. 3. Leave it playing for a few hours. What is the expected behavior? What went wrong? We are developing a media playback application, and stumbled upon an issue where the video content stops playing after few hours of play. We're using Asus ChromeBit for this application -> https://www.asus.com/uk/Chrome-Devices/Chromebit-CS10/ After extensive testing it appears that videos with audio or standalone audio files will not play. Videos with audio do load, but don't start playing, clicking on different spots on video timeline would show the correct frame. Videos without audio channel play as expected. We have tested acc, mp3, amr audio files and mp4 and webm video files with different encodings. Issue persists even after restarting the browser. Only turning the screen off and on or restarting the chromebit it self, removes the issue for a period of time. Let me know if could give more details for debugging this issue. Thanks Did this work before? N/A Is it a problem with Flash or HTML5? HTML5 Does this work in other browsers? Yes Chrome version: 54.0.2790.0 Channel: stable OS Version: 51.0.2704.103 (Official Build) (32bit) Flash Version: Shockwave Flash 22.0.0.192-r1
,
Jul 8 2016
Please check chrome://media-internals to see what the reported error is for your player.
,
Jul 12 2016
Start for all HD video player jwplayer campaign Support
,
Jul 20 2016
epoplavskis@2point0concepts.com, do you mean video in #1 will auto stop after a few hours of playing?
,
Aug 15 2016
no response from bug opener for > 3 weeks. close this bug.
,
Aug 18 2016
Hi, thank you guys for your responses, but in latest continues tests my team wasn't able to replicate this issue. I supposed the chrome os update has solved it, but we wanted to make sure that's the case with more testing. This ticket can be closed. Thanks again for your time. |
|||
►
Sign in to add a comment |
|||
Comment 1 by epoplavs...@2point0concepts.com
, Jul 8 2016