-
Notifications
You must be signed in to change notification settings - Fork 6k
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
Crash in TextRenderer
when rendering stream with single subtitle
#8017
Comments
I'm not able to reproduce this crash. I tried with the following WebVTT file:
And played it in the demo app at 2.12.0 using this JSON snippet:
The video played fine and displayed the subtitle as expected on the screen. I didn't see any suspicious stack traces in logcat. Are you able to reproduce the behaviour you see in the ExoPlayer demo app? Can you provide more info about your setup to help us reproduce and investigate? |
Indeed I can't repro with the VTT example you posted. I suspect it is because the VTT input buffer does not set I am able to reproduce reliably with the CEA-608 subtitles in the example below. Here, the very first time the decoder grabs captions, the input buffer has
|
Thanks, I can repro with that media. (side note, I had to tweak the URL slightly, think it should be |
I've sent a fix for this - thanks for reporting |
Any updates, when this is going to be released? We're stuck on this crash now. |
@ojw28 is putting together 2.12.1 which will include this fix - no eta I'm afraid. |
[REQUIRED] Issue description
We get an NPE in 2.12.0 when the
TextRenderer
tries to render a stream with a single subtitle:I think this was introduced with the null checks added here: 0efec5f#diff-2a869b1d2a8dabec5def4e6e02d2bd18
It is possible to call
getNextEventTime()
on the firstrender()
ifnextSubtitle.isEndOfStream()
.[REQUIRED] Reproduction steps
It is difficult for us to share a stream in the clear that reproduces this.
[REQUIRED] Link to test content
See above.
[REQUIRED] A full bug report captured from the device
Happy to do this upon request.
[REQUIRED] Version of ExoPlayer being used
2.12.0
[REQUIRED] Device(s) and version(s) of Android being used
Any
The text was updated successfully, but these errors were encountered: