Aditional chrome startup flags for complex pages or low power Pi Zero W

[Physics-Dude]

Chrome would claim the tab is unresponsive/taking too long on my Raspberry Pi Zero W without these startup optional flags. I'm using it for a live radar image from embed.windy.com, so it's asking a lot of the hardware.

--disable-smooth-scrolling 
--disable-low-res-tiling 
--enable-low-end-device-mode 
--disable-composited-antialiasing 
--noerrdialogs 
--enable-gpu-rasterization 
--fast 
--fast-start 
--disk-cache-dir=/dev/null 

As an aside, I am not sure if any of these flags are still supported in chrome. They are a holdover from my own DIY kiosk project from previous years. That project recently failed with segfaults and illegal instructions after I decided to run updates.

[Physics-Dude]

For myself and others to reference in the future; using a Pi Zero 2 W with Raspberry Pi 4 support (RC4) release, my chrome startup flags in ~./xsession are as follows.

chromium-browser \
  --start-fullscreen \
  --window-position=9000,9000 \
  --disable-infobars \
  --disable-smooth-scrolling \
  --disable-low-res-tiling \
  --enable-low-end-device-mode \
  --disable-composited-antialiasing \
  --noerrdialogs \
  --enable-gpu-rasterization \
  --fast \
  --fast-start \
  --disk-cache-dir=/dev/null \
  --check-for-update-interval=1 --simulate-critical-update \
  $URL &