[Oneplayer] Live streaming going in loop on Chromium/Blink web browser engine

[Digitalone1]

In the last months I noticed a weird issue on Oneplayer. When I watch a live streaming on an OTT Italian service, sometimes the reproduction goes in loop replaying the latest 1-2 seconds for 4-5 times and then it returns to the live position.

I'm observing this issue from February, but it only happens on Chromium browsers (Blink engine). No matter which OS I use (Windows or Linux), it's quite easy to reproduce, even if it happens randomly.

The only way to avoid this issue is to use a Gecko-based browser, Firefox or one of its derivatives. I watched hours of streaming without these loops happening on Firefox, but as soon as I switch to a Chromium browser, they occur randomly.

This is the current version I experienced them on Brave browser:

Commit Hash: e1e581a
OnePlayer UI version: 7.9.1
CorePlayer:rx 4.5.0-canal.2026033100

I exclude it's an issue of the latest Chromium releases because I installed an old version released in December 2025, but these loops are still happening. It's likely something related to the latest Oneplayer versions (released in late January or early February 2026) that conflict with Blink web engine.

I hope this report can help to solve the issue in next releases. A reply would be appreciated.

[peaBerberian]

Hi @Digitalone1,

First sorry for the delay (and for the absence of answer for your previous issue, that I'll take again a look at), I sometimes first notice a new GitHub issue much later while going through e-mails / notifications outside work hours and then forget about it.

---

That issue is not known to us and interesting that it's relatively new, thanks for the checks.

replaying the latest 1-2 seconds for 4-5 times and then it returns to the live position

It could be multiple things but to narrow it down: you have thus ~4-10 seconds of replayed playback before being "un-stuck"?Do you see a temporary black screen before we're back to live? Is it strictly the same 1-2 seconds being replayed?

When it is replaying the same 1-2 seconds, is there a spinner on screen? Does it happen at specific boundaries (e.g. between programs, at ad breaks etc.?)

If you reproduce it again, you could take a capture (preferably video, but image would be very helpful too) of the RxPlayer debugging information panel (on the right player it's right click on the player > debugging information > enable RxPlayer debug panel:

---

There are many possible theories here:

• First, media playback is not only dependent on the client+browser version, there's a large part of the media pipeline linked to OS-provided API and drivers that may change e.g. at windows updates.

  So it's still a possibility to have a new issue due to such a regression.

• Second there could be an encoding quirk in that stream that leads to a very minor media-related issue only on chromium-based browsers then leading the RxPlayer to worsen the situation (e.g. one of its heuristics could wrongly assume that we're stuck and try strategies to un-stuck it, one of which is seeking back in the stream).

  For example from the POV of the RxPlayer, the currentTime of the video tag might not be advancing despite the fact that playback is progressing from the browser POV. This could lead to this type of behavior. Often, the RxPlayer ends up "reloading" the content if other strategies (like seeking) don't work, which is why I asked about the black screen possibility.

• It's also possible that there's just a regression in the RxPlayer or OnePlayer that provokes this, e.g. when handling boundaries of multiple "Period"s in the content (sub-divisions of the content, like we could have between programs / ad breaks etc.)

---

To be honest the best information would be logs here but it's a bit more involved than just taking screenshots of the debug panel.

If you know how to reproduce it and have time on your hands for this, you can:

• Open the inspector on the corresponding page
• Search in all files (in Chrome: Ctrl+Shift+f)
• look for __RX_PLAYER_DEBUG_MODE__. There should be a single file where this is defined.
• Put a breakpoint just before the first mention of it.
• Reload the page and re-run the content to have the breakpoint in place
• While blocked in the breakpoint, type window.__RX_PLAYER_DEBUG_MODE__ = true in the console and then exit that breakpoint
• you now have all logs

However note that our logs are very verbose.

---

Anyway thanks for the issue and sorry about not having answered this issue (and especially the january one), sooner

[Digitalone1]

Hi @peaBerberian.

It could be multiple things but to narrow it down: you have thus ~4-10 seconds of replayed playback before being "un-stuck"?Do you see a temporary black screen before we're back to live? Is it strictly the same 1-2 seconds being replayed?

When it is replaying the same 1-2 seconds, is there a spinner on screen? Does it happen at specific boundaries (e.g. between programs, at ad breaks etc.?)

I did not see a temporary black screen when it happened. I did not count how many time the same playback has been repeated, but I can confirm that it's at least 3 times. Then sometimes it can be 5 times, other 6-7 times...

I did not remember if there was a spinner on the screen (for a long time I'm just using Firefox because it happens on Chromium browsers), but surely there wasn't a pause/suspension. The playback goes without interruptions, just the latest 1-2 seconds are replayed for almost 4-5 times.

It does not happen at specific boundaries, it's totally random. The platform I use does not have ad breaks (I mean the ones injected by the platform, not the ones on the live channels). On Brave, in order to solve past issues, I disabled the Brave Shield, so I may see platform ad breaks, but the issue still happens. On Firefox (Window 11) I have uBlock origin enabled and I can't reproduce the issue, so it's not even an issue related to the ad block.

I have also to specify (if it's not clear from the open post), that this issue happens on live streaming channels, not video contents on demand (the platform is Timvision which has many live channels and uses the Canal+ framework). At the moment I don't know if it happens on VOD contents too, since I only watch live channels recently on this platform.

If you reproduce it again, you could take a capture (preferably video, but image would be very helpful too) of the RxPlayer debugging information panel (on the right player it's right click on the player > debugging information > enable RxPlayer debug panel

Tomorrow I'll try.

• First, media playback is not only dependent on the client+browser version, there's a large part of the media pipeline linked to OS-provided API and drivers that may change e.g. at windows updates.

Okay, but I noticed this issue on:

• Brave Browser on Linux (Widevine)
• Google Chrome on Linux (Widevine)
• Brave Browser on Windows 11 (Widevine)
• Edge on Windows 11 (Playready)

Considering that I can't reproduce this issue on Firefox, which I tried on both Linux and Windows, I think it's not related to the OS, but to rx-player and the browser engine (it happens on Blink, not Gecko). I can't test a Webkit browser (don't have Apple devices).

For example from the POV of the RxPlayer, the currentTime of the video tag might not be advancing despite the fact that playback is progressing from the browser POV. This could lead to this type of behavior. Often, the RxPlayer ends up "reloading" the content if other strategies (like seeking) don't work, which is why I asked about the black screen possibility.

I do not see black screens.

• While blocked in the breakpoint, type window.__RX_PLAYER_DEBUG_MODE__ = true in the console and then exit that breakpoint
• you now have all logs

Okay, but where these logs are placed? Should I copy something (maybe the console?) or should I look to a specific file?

Anyway, it's not easy to reproduce because it's totally random.

Thanks for your interest in looking into it.

[peaBerberian]

Thanks

I use does not have ad breaks (I mean the ones injected by the platform, not the ones on the live channels).

Note that I was actually talking only about the live channels one, not about some other external ads loaded by the platform itself.
Depending on the content, what could be assumed to be "just the ads of the channel" can actually be explicit ad breaks at the media streaming level [targeted or not], play smoothly just like the rest of the content, and not be blocked by today's adblockers.

Here that question only mattered because those can be the main source of the "boundaries" I was thinking of (which are more technically referred as "DASH Periods"), but if you did not notice a pattern, that must not be it.

Okay, but where these logs are placed? Should I copy something (maybe the console?) or should I look to a specific file?

It's inside the console, as regular logs. But if it's not easy to reproduce, you may be having a lot of logs before reproducing this, this may not be practical for you :/
The debug page when/if reproducing is also very helpful.

---

If there's no black screen that's interesting. The RxPlayer may not consider this as a "freeze" (the content does not play from its point of view), this could be mostly the browser having issues decoding.

Another possible culprit could be that it happens at specific quality switches also? This can be seen on the debug window with the colors on the vbuf graph (one color = one quality basically, with the red line being the current position).

[Digitalone1]

Note that I was actually talking only about the live channels one, not about some other external ads loaded by the platform itself. Depending on the content, what could be assumed to be "just the ads of the channel" can actually be explicit ad breaks at the media streaming level [targeted or not], play smoothly just like the rest of the content, and not be blocked by today's adblockers.

Here that question only mattered because those can be the main source of the "boundaries" I was thinking of (which are more technically referred as "DASH Periods"), but if you did not notice a pattern, that must not be it.

Okay, but no, I don't even think Timvision uses the "explicit ad breaks at the media streaming level". And I remember that the replays were showing during programs.

It's inside the console, as regular logs. But if it's not easy to reproduce, you may be having a lot of logs before reproducing this, this may not be practical for you :/ The debug page when/if reproducing is also very helpful.

I'll try to take these logs, if I'm lucky to reproduce on Brave.