Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Paused video keeps writing log lines about buffer pruning #1406

Closed
wilaw opened this issue May 20, 2016 · 0 comments
Closed

Paused video keeps writing log lines about buffer pruning #1406

wilaw opened this issue May 20, 2016 · 0 comments
Labels
Milestone

Comments

@wilaw
Copy link
Member

wilaw commented May 20, 2016

When a stream is paused , interval for buffer pruning keeps writing log lines.

Steps to repro:

  1. Use reference client
  2. Play http://rdmedia.bbc.co.uk/dash/ondemand/testcard/1/client_manifest-events.mpd for 10s.
  3. Pause
  4. Wait 2 minutes
  5. View console logs.

Example output:

Debug.js:108 [93900] SegmentTemplate: 68 / 3600
2016-05-20 10:45:59.802 Debug.js:108 [94300] Buffered Range: 0 - 70.015999
2016-05-20 10:45:59.803 Debug.js:108 [94301] Prior to making a request for time, NextFragmentRequestRule is aligning index handler's currentTime with bufferedRange.end. 70 was changed to 70.015999
2016-05-20 10:45:59.804 Debug.js:108 [94302] Getting the request for audio time : 70.015999
2016-05-20 10:45:59.804 Debug.js:108 [94302] Index for audio time 70.015999 is 34
2016-05-20 10:45:59.804 Debug.js:108 [94302] SegmentTemplate: 68 / 3600
2016-05-20 10:45:59.805 Debug.js:108 [94303] Getting the next request at index: 35
2016-05-20 10:45:59.805 Debug.js:108 [94303] SegmentTemplate: 70 / 3600
2016-05-20 10:46:00.187 Debug.js:108 [94685] Buffered Range: 0 - 71.999999
2016-05-20 10:46:15.658 Debug.js:108 [110156] try to prune buffer
2016-05-20 10:46:45.662 Debug.js:108 [140160] try to prune buffer
2016-05-20 10:47:15.663 Debug.js:108 [170161] try to prune buffer
2016-05-20 10:47:45.662 Debug.js:108 [200160] try to prune buffer
2016-05-20 10:48:15.663 Debug.js:108 [230161] try to prune buffer
2016-05-20 10:48:45.665 Debug.js:108 [260163] try to prune buffer
2016-05-20 10:49:15.665 Debug.js:108 [290163] try to prune buffer
2016-05-20 10:49:45.669 Debug.js:108 [320167] try to prune buffer
2016-05-20 10:50:15.671 Debug.js:108 [350169] try to prune buffer
2016-05-20 10:50:45.671 Debug.js:108 [380169] try to prune buffer
2016-05-20 10:51:15.674 Debug.js:108 [410172] try to prune buffer
2016-05-20 10:51:45.672 Debug.js:108 [440170] try to prune buffer
2016-05-20 10:53:11.177 Debug.js:108 [525675] try to prune buffer
2016-05-20 10:53:41.179 Debug.js:108 [555677] try to prune buffer
2016-05-20 10:54:11.178 Debug.js:108 [585676] try to prune buffer
2016-05-20 10:54:41.183 Debug.js:108 [615681] try to prune buffer
2016-05-20 10:55:11.184 Debug.js:108 [645682] try to prune buffer
2016-05-20 10:55:41.184 Debug.js:108 [675682] try to prune buffer
2016-05-20 10:56:11.186 Debug.js:108 [705684] try to prune buffer

========= Issue submission guidelines (you may delete the text below after reading it ) =========
Before creating a new issue around a potential bug please:

  1. Check your browser's console for 404s (MPD file or media fragments)
  2. Check for Access-Denied errors which indicates an issue with the server's HTTP access control (CORS)
  3. Please use the Dash Validator (http://dashif.org/conformance.html) to make sure your MPD and media fragments conform before you file an issue.
  4. View the Javascript console to see the debug traces produced by the reference player. They may indicate why your content is not playing.
  5. When you do file an issue please add as much info as possible:
  • Your dash.js, browser and OS system versions
  • Valid MPD test content - ideally the URL to the manifest or a static copy of it if it is not public.
  • The relevant excerpt from the console trace showing the problem.
  • A clear sequence of steps to reproduce the problem.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant