Rogue Frames Randomly Output from PresentData in P00 ETL #556
Description
Randomly get 24 extra frames from P00Heaven. All frames have time in present = 0. Shows in legacy Streamer, new broadcaster, and Main pre-rework. Frames appear to have plausible timestamps for being legitimate.
race condition exists in PresentData. I was expecting something in how service is consuming from the completed queue. But in the normal case presentdata is not marking those frames as complete, and in the failure case it is. so the service is just processing what it gets (as it should), and it is probably presentdata misbehaving somehow by randomly choosing to spit these frames out.
we can see that in either case, the weird frames are added to completed
the difference comes in the failure case, they're also marked ready, but not marked in the base case
Seems limited to this ETL and only affects end of capture. Analyze later to determine discriminating circumstances for the base case and the 24 extra frame case.