When thinking about it a bit more - wouldn't this be "solved" by just always adding Date.distantFuture as the last entry? It's dumb as hell, but.. It doesn't show any increased CPU usage until hitting the last explicit date. Simply appending an unreachable date should do the trick..

Two years ago, I was trying to use TimelineView with explicit dates to drive my UI. I experienced how it ignored the last date, and I found this exact Developer Forum post. I decided to go for a different approach entirely. Now, two years later, I find myself in the exact same situation, and stumble upon the very same post again. TimelineView would be absolutely perfect for what I'm about to do, but .explicit dates still aren't working. I've launched a DTS about it now, let's see if it pans out. It still unexpectedly and perpetually increases the CPU usage when it hits the last explicit date, while also not updating the view.

Did you figure it out? We're seeing the same, seemingly related to the HLS stream's buffer length.