I'll provide one thing I've really noticed
https://lists.ubuntu.com/archives/ubuntu-devel/2022-January/041819.html
I have had an issue with browser extensions for a couple of years in both chromium & firefox; the issue doesn't occur if I don't use these extensions, but does when I do & I prefer using them thus I do.
I've learnt to manage the issue via htop being left running in a terminal window; and when I detect signs of growing-RAM-usage by either browser I confirm with my running htop & then close the browser down.. let the kernel clear up the RAM & when I see evidence of that (again on htop window) I restart the browser(s).
I've not had to do that for awhile thanks to systemd-oomd as the system does it for me
Examples
Feb 15 17:10:20 d960-ubu2 systemd-oomd[949]: Killed /user.slice/user-1000.slice/[email protected]/app.slice/snap.chromium.chromium.82bbbfd7-c79b-4b57-b425-e543631ca054.scope due to memory p>
Feb 15 17:10:22 d960-ubu2 mtp-probe[446025]: checking bus 5, device 89: "/sys/devices/pci0000:00/0000:00:1a.2/usb5/5-2"
Feb 15 17:10:23 d960-ubu2 systemd[5610]: snap.chromium.chromium.82bbbfd7-c79b-4b57-b425-e543631ca054.scope: Consumed 5h 29min 24.000s CPU time.
I've also noticed it killing other apps too
Feb 15 17:10:36 d960-ubu2 systemd-oomd[949]: Killed /user.slice/user-1000.slice/[email protected]/app.slice/snap.telegram-desktop.telegram-desktop.c0a93946-0960-44ed-aeb3-f9903b01056b.scope>
I sit on the development branch, and that's one change I've noticed of late. ie. what I used to do manually (kill the naughty process before it's a problem for me) is now being done automatically; and I just need to restart it 