video buffering issues

[BatmanDrinkingLean]

maybe like twice a day I encounter buffering issues with one video at a time. A video will start buffering and will not start back up, the next few videos usually work fine if i skip the buffering one, but eventually another one will occur in that session.

What cures it for a few hours at least(usually longer) is using the 'wipe cached metadata' option in the settings. If the video is buffering and I use this option the video will start back up where it was buffering.

maybe a solution could be to implement a setting where the cache can be set to automatically wipe after the amount of time set by the user.

[BatmanDrinkingLean]

error i got after encountering a infinite buffer today

[BatmanDrinkingLean]

I have been trying to get the error report again but it won't give it to me. here's a screen recording, idk if this is useful or not. https://flic.kr/p/2q2ZhqQ am i the only one experiencing this? it also happens on my laptop using bluestacks. im on a strong wifi connection with this happening also in both scenarios. would really appreciate the option to have the 'wipe cached metadata' on a timer, I'd probably set it to wipe every hour or maybe after each individual video finishes. this would fix my issue i think.

…

On Thu, Jun 27, 2024, 1:48 AM InfinityLoop1308 ***@***.***> wrote: Please attach the error report (not the screenshot). — Reply to this email directly, view it on GitHub <#305 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BITRFUQ5CZU3KV7E4ZIAU6TZJOYTFAVCNFSM6AAAAABJMGGFKOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJTHEZDMMZZGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[InfinityLoop1308]

@BatmanDrinkingLean The problem is that without a report I am unable to figure out if it is the proper solution - and very likely not.

[InfinityLoop1308]

And, yes, you are the only one who reported this issue. Many users are encountering a similar issue which prevent loading YouTube videos randomly due to its new anti-crawler system, but in that case the app just throw an error and move on.