Chromium container cannot render 3D content on Verdin iMX8M-Mini

vix · March 30, 2022, 3:02pm

Hi @jeremias.tx
I want to add some news on this topic.
Based on your suggestion here I modified the startup script

toradex/kiosk-mode-browser/blob/4fbc3e3465dd1a4d27c29ba7cdd1ad13ce25f7d6/start-browser.sh#L15


      
          
          
# LAUNCHER
          if [ -z "$KIOSK_LAUNCHER" ]; then
              KIOSK_LAUNCHER="chromium"
          fi
          
          
start_chromium() {
              KIOSK_ENV="LIBGL_ALWAYS_SOFTWARE=1 $KIOSK_ENV"
          
          
    # default parms for kiosk mode
              chromium_parms_base="--test-type --allow-insecure-localhost --disable-notifications --check-for-update-interval=315360000 --disable-gpu "
              chromium_parms="--kiosk "
          
          
    # Additional params should be stacked chromium_parms_extended="$chromium_parms_extended ..."
              chromium_parms_extended=""
          
          
    # FIXME: TOR-1426: work around seccomp-bpf failures in chromium.
              chromium_parms_extended="$chromium_parms_extended --disable-seccomp-filter-sandbox"
          
          
    for arg in "$@"
              do

removing --disable-gpu
adding --enable-features=UseOzonePlatform --ozone-platform=wayland as explained in the Igalia document I mentioned above

In this way the CodeSandbox demo runs inside the container, but the performance are poor.
The performance becomes poorer if I set the parameter --in-process-gpu (I don’t know exactly its purpose, but some online resources suggest to use it).
So I think that basically the road seems promisingly, but some more tuning and test is necessary (to understand which parameters should be passed to Chromium).

A more complex 3D example doesn’t work with client exception (but this can be memory overflow or other issues - investigation needed).