Malicious Stream Causing GPU Crashes and Node Disruptions

Several orchestrators have noticed, in recent weeks, the existence of one or more streams causing GPU crashes (cuda error) which leads to the loss of all running streams, and even to the crash of the transcoder/node. The stream then switches to another orchestrator, causing the same results.

I am concerned about the impact of this kind of event on the quality of the network, and the possibility that such streams could also be voluntarily injected into the network.

Following the discussion yesterday evening on the watercooler chat, Doug considered the possibility that the Broadcaster node could identify the stream and delete it automatically to prevent it from spreading, but if the stream was injected voluntarily, it might be better to be able to detect it and block it at the orchestrator level.

I have not been able to identify the responsible stream, and this event remains rather rare, but when it happens, several orchestrators usually report it on Discord.

Start by reviewing the orchestrator reports and the related Discord discussion to identify the offending stream and determine whether the failure is in the Broadcaster node or orchestrator handling. The issue names no files or tests; the work is complete only when a confirmed detection and prevention approach is defined and validated against the GPU crash and node disruption.