YouTube is experiencing a new performance issue that is significantly impacting its usability on computers, particularly those with limited processing power or RAM. Google has been actively working on their code, aiming to reduce the effectiveness of ad blockers. Combined with recent interface changes, this has led to YouTube performance degrading to the point of crashing.
Users are reporting various issues depending on their system, browser, and individual usage patterns, including freezes, screen lock-ups, and playback stuttering due to CPU saturation. Additionally, RAM consumption has spiked to over 7 GB for a single YouTube tab. The problem has been observed across different browsers, including Firefox, Brave, and Microsoft Edge, strongly suggesting a flaw within YouTube’s interface rather than a browser-specific bug.
Mozilla Confirms YouTube Interface Bug, Not Browser Issue
Research from Bugzilla, Mozilla’s public bug tracking system, has provided significant insights. A report titled “YouTube enters a loop where images take longer and longer to load” was initially classified as a web compatibility problem. The report detailed similar user experiences and linked Firefox performance profiles for analysis of YouTube playback.
The technical root of the bug appears to lie within the ytd-menu-renderer component, which is part of the YouTube interface located below the video player. This component manages buttons like “like,” “dislike,” “share,” and other controls. Its flexible logic attempts to determine if all buttons fit within the available width. If there isn’t enough space, it hides a button. However, hiding a button alters the available container width, causing the code to believe there’s now space to display it again. It then restores the button, leading to an overflow, which prompts it to hide the button again, creating a repeating cycle.
This loop is not merely a visual anomaly. In modern browsers, any change in the size, position, or visibility of elements forces the rendering engine to recalculate the page layout, repaint elements, and update internal states. When this process is continuously triggered via requestAnimationFrame, the browser enters a reflow loop. A technical comment on Bugzilla also noted that each requestAnimationFrame callback could schedule two new callbacks for the next cycle, cumulatively worsening the problem.
Repeating YouTube Interface Loop Leads to Increased CPU and RAM Usage
In practice, affected users observed a progressive degradation of their YouTube tabs. Initially, playback stuttering would occur, followed by unresponsive player controls, then a frozen tab, and eventually, memory consumption could increase to the point of forcing a manual closure. One Bugzilla report described a hanging tab where video and audio stopped after a few seconds, with RAM usage continuously climbing, leading to memory exhaustion or manual process termination.
Another associated report detailed cases of excessive CPU usage, constantly growing RAM consumption, and completely blocked YouTube tabs. One user tested standard Firefox, Firefox Developer Edition, Waterfox, and Brave. They observed that the problem did not manifest identically across all browsers, which initially complicated the diagnosis. Nevertheless, the prevailing hypothesis was that of a bug within YouTube’s web interface, rather than a flaw in the video engine or the codec used by each browser.
At the time of writing, neither Google nor YouTube has publicly confirmed the cause of the issue. However, the Bugzilla thread was updated earlier today with a note stating that YouTube had implemented a mitigation and that the problem “should no longer be occurring,” with the bug’s status changed to “RESOLVED FIXED.” If you are still experiencing this issue, you may need to force an update of your web browser.
