From 3e07024c8e4a76cd22596b7783cd3bf92df7fea5 Mon Sep 17 00:00:00 2001
From: IgorA100 <igora100@gmail.com>
Date: Fri, 5 Jun 2026 00:28:10 +0300
Subject: [PATCH] Prevent pointless setInterval(this.statusCmdQuery) calls for
 "frozen" objects. (MonitorStream.js)

This PR doesn't fix the root cause of the issue, but addresses the consequences.
I spent time investigating the problem, but I couldn't figure out the root cause because it's difficult to debug.
Perhaps I'll revisit this issue later.
For now, let's leave it at that.
---
 web/js/MonitorStream.js | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/web/js/MonitorStream.js b/web/js/MonitorStream.js
index 821e7ef58..2e95f3afe 100644
--- a/web/js/MonitorStream.js
+++ b/web/js/MonitorStream.js
@@ -1564,6 +1564,12 @@ function MonitorStream(monitorData) {
         .fail(logAjaxFail);
 
     if (this.Go2RTCEnabled && ((!this.player) || (-1 !== this.player.indexOf('go2rtc')))) {
+      if (!this.element.currentMode) {
+        // TODO: For some reason, when switching monitors very quickly on the Watch page while using go2rtc, "this.statusCmdTimer" sometimes doesn't clear.
+        // This is likely due to the generation of the <video> tag in video-rtc.js.
+        clearInterval(this.statusCmdTimer);
+        return;
+      }
       if (-1 !== this.element.currentMode.toLowerCase().indexOf('mse')) {
         $j('#delay'+this.id).removeClass('hidden');
         this.manageMSESocket(this.element.video, this.element.ws, this.element.ms);