-
Notifications
You must be signed in to change notification settings - Fork 1.2k
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Closing incorrect source for new partial response without cache #43
Comments
Change the HttpProxyCache.responseWithoutCache() method to like this :
|
danikula
changed the title
A serious bug might cause MediaPlayer stop work
Closing incorrect source for new partial response without cache
Jul 29, 2016
danikula
added a commit
that referenced
this issue
Jul 29, 2016
danikula
added a commit
that referenced
this issue
Jul 29, 2016
danikula
added a commit
that referenced
this issue
Jul 29, 2016
Fixed here |
This was referenced Jul 29, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This library use one HttpProxyCacheServerClients for same url ,for every single request,the HttpProxyCacheServer start a new thread to handle the request,so there would be more than one thread running with HttpProxyCacheServerClients.processRequest().
For partial request,it will go like this:
HttpProxyCacheServerClients.processRequest()->
HttpProxyCache.processRequest()->
HttpProxyCache.responseWithoutCache(),
here is the code of "responseWithoutCache()" method:
At the finally block,the "source.close()" will close the source might being used in ProxyCache.readSource() if there is a another request running with HttpProxyCache.responseWithCache(),so the cache thread will stop,then the MediaPlayer will get no data return.
I think what the author really want to do is to close the source in the try block.
PS:The log when the MediaPlayer stop work:
PPS:I replaced the video url in the log.
The text was updated successfully, but these errors were encountered: