SVG rendering fragmented on Torizon using torizon/weston-vivante:2.7.2 and torizon/chromium:2.6.0 containers

Hi all!

We are currently experiencing some rendering issues with SVG graphics. Our setup is as follows:

  • Verdin iMX8MP Q 4 GB WB IT
  • Dahlia V1.1A
  • hp display connected via HDMI
  • TorizonCore 5.6.0+build.13
  • customized SplashScreen (company logo)
  • docker containers torizon/weston-vivante:2.7.2 and torizon/arm64v8-chromium:2.6.0

SVG images are heavily fragmented as can be seen in the following screenshot (taken with VNCViewer and shows the rendered result from commanding chromium to navigate to svgrepo.com):

Since I am not sure if we actually made something wrong within our configuration I would like to ask if this is an actual issue with the container image or just something on our side. The issue might somehow be related to the torizon/arm64v8-chromium:2.6.0 image since the SVG rendering is fine in older versions of the container image (e.g. torizon/arm64v8-chromium:2.5). We would really like to make use of the added HW acceleration in the 2.6.0 chromium image.

Our docker-compose.yml looks as follows:

version: "2.4"

services:

    kiosk:

        container_name: Kiosk

        image: torizon/arm64v8-chromium:2.6.0
        #image: torizon/arm64v8-chromium:2.5

        restart: always

        command: https://www.svgrepo.com/

        depends_on:
            weston:
                condition: service_started

        device_cgroup_rules:
            - c 199:* rmw
            - c 226:* rmw

        environment:
           - MACHINE

        security_opt:
            - seccomp:unconfined

        shm_size: 256mb

        volumes:
         - /tmp:/tmp
         - /var/run/dbus:/var/run/dbus
         - /dev/dri:/dev/dri
         - /dev/galcore:/dev/galcore

        network_mode: host

    weston:

        container_name: Weston

        cap_add:
        - CAP_SYS_TTY_CONFIG

        device_cgroup_rules:
        - c 4:* rmw
        - c 13:* rmw
        - c 199:* rmw
        - c 226:* rmw

        environment:
        - ACCEPT_FSL_EULA=1
        #- ENABLE_VNC=1

        image: torizon/weston-vivante:2.7.2

        platform: linux/arm64

        network_mode: host

        restart: always

        volumes:
            - /tmp:/tmp
            - /dev:/dev
            - /run/udev:/run/udev

The screen resolution is 1920x1080:

Weston    | [07:56:22.957] Output HDMI-A-1 (crtc 33) video modes:
Weston    |                1920x1080@60.0, current, 148.5 MHz

Best regards

Hi @bgo ,

We were able to reproduce your result on our side with the same Verdin SoM and Dahlia model as yours. We used your Docker Compose yaml file for the tests and we tested on a vanilla TorizonCore 5.6.0 as well as the latest 5.7.0 nightly release.

From our initial findings this looks like an issue with our container image, possibly affecting other iMX8 modules with TorizonCore, as the problem also happened on a Colibri iMX8X during our tests.

We’re currently investigating possible causes for this strange behavior. Thank you for reporting this!

In the meantime, could you see if this problem persists using Cog instead of Chromium: Web Browser / Kiosk Mode with TorizonCore | Toradex Developer Center? From our tests the SVG graphics were rendered properly with Cog and it supports hardware acceleration, so it could be a workaround.

Let me know if this helps you.

Best regards,
Lucas Akira

1 Like

Hi @lucas_a.tx

thank you for investigating!
I followed your instructions using Cog and the SVG graphics are being rendered as expected - thank you for the workaround! We will use it and wait for the next update on your Chromium container :slight_smile:

Best regards

2 Likes

Hi @bgo, thanks a lot for the update!

We’ll come back to you once we have any news for you to use Chromium.

Best regards,

1 Like

Hi @gclaudino.tx , thank you - any news on your chromium container is much appreciated! Can you estimate a time schedule for it?
Best regards,

Hi @bgo,

I can’t provide you with a timeframe as of today. However, I can assure you that the internal tickets have been created and the team is aware of this problem.

Hi @gclaudino.tx , thank you! I will look forward for any news :grinning:

1 Like

Hi @bgo !

Unfortunately, we still are waiting for news about the Chromium issue. Thanks for your patience.

Best regards,

1 Like