On Fri May 8 01:37:25 2026 +0000, Paul Gofman wrote:
44066.349:0020:0160:trace:pulse:pa_streams_timer_cb Buffer comparison: pa_held_bytes: 0, held_bytes: 19200, diff: 19200 I don't have this trace in my code, there is something else on top. The immediate reason is apparently that something went very wrong with the scheduling next time for pa_streams_timer_cb() but I can't guess what exactly from existing info. What exactly are you building, can we start with just upstream and my patch if possible? If that reproduces the issue I could probably add a bit more logging (I'd started from checking that pa_stream_get_time() succeeds in pa_streams_timer_cb and then logging stream_time and all the conditions there (just_underran, just_started), and what next_timer it actually ends up with right before pa_context_rttime_restart()). But looking at the code, whatever goes with the stream time I am not sure how that can happen that pa_streams_timer_cb is just never called again throughout some seconds (even if time adjustment is completely wrong it is limited in value). That's why it is important to first remove any other changes.
-- https://gitlab.winehq.org/wine/wine/-/merge_requests/10792#note_139170