Bugzilla

Sometimes, and I don't know exactly when or how, I run into situations where Firefox Content processes become more or less completely unresponsive (the browser UI seems to stay responsive). I have captured a profile at one instance, see https://share.firefox.dev/3XdKtB8 - profile was created on macOS 14.5 (23F79) on a 2021 16 inch MacBook Pro with the M1 Max.

You'll see in that profile that all three content processes jank, a lot. IIRC, I had the Discord and the schub.social tabs in one window, and the YouTube tab in another. The YouTube tab was on a second screen, maximized window, playing a video. The YouTube window was in plain view, but didn't have focus (focus was likely on the text editor). The other window was in the background, too, I think - but I don't fully remember.

When I wanted to select a new video, I noticed that the tab's contents were pretty unresponsive (it took a solid 30 seconds for it to load a new video). I also noticed that the other tabs were unresponsive as well, but starting a profile recording worked fine. There was no elevated CPU or memory usage, and no significant storage I/O. Besides a text editor and a terminal, I don't had any resource-intensive applications running (although, to be fair, the text editor is VSCode...). The system remained responsive, and other applications stayed fast, too.

Sometimes, and I don't know exactly when or how, I run into situations where Firefox Content processes become more or less completely unresponsive (the browser UI seems to stay responsive). I have captured a profile at one instance, see https://share.firefox.dev/3XdKtB8 - profile was created on macOS 14.5 (23F79) on a 2021 16 inch MacBook Pro with the M1 Max.

You'll see in that profile that all three content processes jank, a lot. IIRC, I had the Discord and the schub.social tabs in one window, and the YouTube tab in another. The YouTube window was on a second screen, maximized window, playing a video. The YouTube window was in plain view, but didn't have focus (focus was likely on the text editor). The other window was in the background, too, I think - but I don't fully remember.

When I wanted to select a new video, I noticed that the tab's contents were pretty unresponsive (it took a solid 30 seconds for it to load a new video). I also noticed that the other tabs were unresponsive as well, but starting a profile recording worked fine. There was no elevated CPU or memory usage, and no significant storage I/O. Besides a text editor and a terminal, I don't had any resource-intensive applications running (although, to be fair, the text editor is VSCode...). The system remained responsive, and other applications stayed fast, too.