I know this was taken out in 0e188cd
but the lack of it makes it a lot harder to forcekill in case the process crashes without recovery\
Both these tabs share a process, one's just been removed from the main window seconds before screencap

I usually just taskkill /f /pid <x> whatever process these run, which allows me to restore these tabs in a fresh process

There now exists no relatively easy way to kill these processes, you have to remove all tabs that aren't responding manually, then you won't hit an issue where the browser makes more tabs on this unresponsive process
Regardless that about:performance takes a considerable time to load pages, it does not contain those that are unresponsive. Otherwise using a process of elimination for webpages in that list, and striking out waterfox processes which PIDs do not appear works but oh god it's so horrid to do
I killed the process for ublock origin in the process :rofl:
An option for configuring the behaviour would be best, I think.
Yeah, I can definitely understand the need for it to be optional, since a majority of users would not even require it, since most the time it just comes down to a cosmetic thing
Apologies: when I raised #340 I was not aware of some of the use cases.
This screenshot (originally from something other than 340) was my first ever sight of 'Â -Â e10s' against a tab, and there was no PIDÂ number:

– if there had been a PID number in the shot, I would have thought more carefully about the issue.
Makes sense, The code for it would only print the PID if there were multiple processes
if (tab.linkedBrowser.frameLoader &&
Services.appinfo.maxWebProcessCount > 1) {
label += " (" + tab.linkedBrowser.frameLoader.tabParent.osPid + ")";
}
The removal was intentional. WONTFIX, probably.
Could this me made a webextension 🤔