Skip to content
This repository has been archived by the owner on Dec 10, 2020. It is now read-only.

Don't null out the throughput timer, just reset it #125

Merged
merged 1 commit into from
Oct 2, 2014

Conversation

dmlap
Copy link
Member

@dmlap dmlap commented Oct 2, 2014

It's not necessary to null out the throughput timer and it could be dereferenced if the src is changed while a seek is still "in-flight". Resetting it ensures it is stopped and zeroed and it can be garbage collected along with the rest of the HTTPVideoProvider. This was causing errors in videojs-contrib-hls when the source was changed quickly after a seek was requested.

It's not necessary to null out the throughput timer and it could be dereferenced if the src is changed while a seek is still "in-flight". Resetting it ensures it is stopped and zeroed and it can be garbage collected along with the rest of the HTTPVideoProvider. This was causing errors in videojs-contrib-hls when the source was changed quickly after a seek was requested.
@gkatsev
Copy link
Member

gkatsev commented Oct 2, 2014

LGTM

@dmlap
Copy link
Member Author

dmlap commented Oct 2, 2014

Specifically, reset() in Netstream.Status.SeekNotify was exploding.

@tomjohnson916
Copy link
Contributor

yeah LGTM, not sure why it was originally like that.

dmlap added a commit that referenced this pull request Oct 2, 2014
Don't null out the throughput timer, just reset it
@dmlap dmlap merged commit a41493b into master Oct 2, 2014
@dmlap dmlap deleted the hotfix/throughput-null branch October 2, 2014 17:56
@heff
Copy link
Member

heff commented Oct 15, 2014

@dmlap this could use a change log entry

heff added a commit to heff/video-js-swf that referenced this pull request Oct 15, 2014
…p some other changelog formatting differences.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants