Recurring, systemic bug pattern: "[recorder] sample of track 1 received too late, discarding"

Which version are you using?

v1.20.1

Which operating system are you using?

Linux amd64 standard

Describe the issue

My VPS disk has been filling up with lots of log messages from MediaMTX lately. As of today, my mediamtx.log file is consuming 17.5 GB mostly of these annoying messages:

{"timestamp":"2026-08-25T13:35:33.128536186Z","level":"WAR","message":"[path XYZ1] [recorder] sample of track 1 received too late, discarding"} {"timestamp":"2026-08-25T13:35:33.1285551Z","level":"WAR","message":"[path XYZ5] [recorder] sample of track 1 received too late, discarding"} {"timestamp":"2026-08-25T13:35:33.131485324Z","level":"WAR","message":"[path XYZ3] [recorder] sample of track 1 received too late, discarding"} {"timestamp":"2026-08-25T13:35:33.131552061Z","level":"WAR","message":"[path XYZ2] [recorder] sample of track 1 received too late, discarding"} {"timestamp":"2026-08-25T13:35:33.132094351Z","level":"WAR","message":"[path XYZ4] [recorder] sample of track 1 received too late, discarding"} {"timestamp":"2026-08-25T13:35:33.133527057Z","level":"WAR","message":"[path XYZ6] [recorder] sample of track 1 received too late, discarding"} {"timestamp":"2026-08-25T13:35:33.134173881Z","level":"WAR","message":"[path XYZ9] [recorder] sample of track 1 received too late, discarding"} {"timestamp":"2026-08-25T13:35:33.136467186Z","level":"WAR","message":"[path XYZ7] [recorder] sample of track 1 received too late, discarding"} AND SO ON... ... For now, as a temporary solution, I implemented a logrotate config to clean that log every 24 hours, but this is just a workaround. So, how to finally solve this issue/bug? Thanks.

Describe how to replicate the issue

1. start the MediaMTX
2. publish with several paths
3. record normally

MediaMTX configuration

MediaMTX logs

No response

Packet dump

No response