When loading some HLS videos, the value of duration or currentPosition is displayed/processed incorrectly.

[Kofeins]

Media3 Version

ExoPlayer 2.18.6

Devices that reproduce the issue

Pixel 4 XL API 33 Pixel 6 API 32 Pixel 4 XL API 31 Pixel 4 XL API 29

Devices that do not reproduce the issue

No response

Reproducible in the demo app?

Not tested

Reproduction steps

1. Load HLS video: https://bitdash-a.akamaihd.net/content/sintel/hls/playlist.m3u8
2. Rewind to the end of the video

Expected result

The values of Player.currentPosition and Player.duration are equal:

Player.currentPosition = 14:48

Player.duration = 14:48

Actual result

Player.currentPosition exceeds Player.duration and continues to increase until 15:05

On playback finished:

Player.currentPosition = 15:05

Player.duration = 14:48

Bug visualization(currentPosition > duration):

Media

Test URL = https://bitdash-a.akamaihd.net/content/sintel/hls/playlist.m3u8

My demo app using ExoPlayer2 on Google Drive: https://drive.google.com/file/d/1ilhc0UhFpuyEBj5_fu5i9Y4YFqVQBiBx/view?usp=share_link

Bug Report

• [ ] You will email the zip file produced by adb bugreport to dev.exoplayer@gmail.com after filing this issue.

[saket]

I've seen this happen with MP4 videos as well. Here's one example: https://cdn.masto.host/androiddevsocial/media_attachments/files/110/900/494/975/751/021/original/e01d435e9f334483.mp4

Should ExoPlayerImpl#getCurrentPosition() manually ensure that its value never exceeds getContentDuration()?