The "GPU Process" in both Firefox and Chromium is notorious for leaking memory on Windows, hogging up precious gigabytes of RAM after some hours or days of use that never gets released, no matter what you click in about:memory or update to the latest GPU driver. It's frustrating having to restart the browser and potentially losing your tabs just to reclaim memory and to have the GPU Process drop down to a few hundred megabytes. Realistically, the memory leak with "GPU Process" will never get fixed, at least not for a decade, as I've seen on Bugzilla the progress and the explanations for how difficult it would be to try to deal with that issue, so the next best thing in the interim would be to have this manual workaround that Chromium has. Not being able to quickly restart "GPU Process" in the browser's Task Manager (or elsewhere) without restarting the browser is a deal-breaker for me, hence why I'm only using a Chromium-based browser now, however if Firefox were to implement such a feature then I'd almost certainly go back to Firefox.