At least on our ram limited work VMs I literally can't launch Chrome without it crashing on launch. Firefox runs with no issues dozens of tabs, although occasi

At least on our ram limited work VMs I literally can't launch Chrome without it crashing on launch. Firefox runs with no issues dozens of tabs, although occasionally I do get a tab OOM crash, which restarting Firefox resolves.. And yes, this is even if I completely quit Firefox to ensure Chrome gets as much RAM as possible. If I've just restarted the machine, sometimes I can launch Chrome. Chrome print preview never renders about 90% of the time when I am able to launch it. Firefox, no issues. On a large complex page, when Chrome does manage to launch and print preview does load, it takes tens of seconds to render. Firefox, no issues. I pretty much just use Chrome when I absolutely have to do a cross-browser test these days. BTW, a Chrome-tangential annoyance is that the code process in VSCode which is basically an embedded browser sometimes runs wild sucking up gigabytes of RAM on another VM dedicated pretty much just to VSCode (and a couple of other minor tools on a lightweight desktop). The irritating thing there is that due to, apparently, a limitation of the blink embed they are using, you can't restrict the RAM available to VSCode to any number (even 100% of system ram) so you basically have to wait for the oomkiller to kill it, or run a parallel monitor to kill it once it sucks up too much ram.