[bug] Poor performance on Arch Linux until Web inspector is opened

[nickheyer]

Describe the bug

Update: 8/11/24
Mostly fixed by switching to wayland. Wayland/nvidia dont get along, so it's causing more issues elsewhere, but at least it's something.

Update: 8/17/24
After building a simple conceptual app with some pretty standard css, I am actually surprised that linux support is even mentioned in the docs and that tauri is being marketed as such. Without some bold warnings, engineering teams may be wasting a good deal of time getting to this same point i've reached, where I've built just enough of an application where I've realized it's basically a non-op on linux. A big LINUX SUPPORT IS VERY EXPERIMENTAL, IT PROBABLY WONT WORK FOR YOU would've saved me and others a lot of time. I get that webkitgtk is at fault here, but that doesn't change the previously mentioned oversights costing people time.

I have been attempting to find a solution to the webkit issues on my Arch Linux installation without adding flags to disable the hw accelerated rendering. I've also been attempting to debug issues caused by the previously mentioned flags.

Using the basic tauri install as an example, I stumbled upon something very interesting when WEBKIT_DISABLE_COMPOSITING_MODE=1...

Normal usage w/ clear artifacts:

Same app, but with inspector open (right click + inspect element):

I've only observed the artifacts using Arch Linux. Here is my nvidia info:

❯ nvidia-smi
Sat Aug 10 23:50:21 2024       
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 555.58                 Driver Version: 555.58         CUDA Version: 12.5     |
|-----------------------------------------+------------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |
|                                         |                        |               MIG M. |
|=========================================+========================+======================|
|   0  NVIDIA GeForce RTX 3080 Ti     Off |   00000000:01:00.0  On |                  N/A |
|  0%   50C    P5             82W /  350W |    1324MiB /  12288MiB |      7%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+                                                                                      

Reproduction

No response

Expected behavior

No response

Full tauri info output

❯ npm run tauri info

> mud@0.0.0 tauri
> tauri info


[✔] Environment
    - OS: Arch Linux Rolling Release X64
    ✔ webkit2gtk-4.0: 2.44.2
    ✔ rsvg2: 2.58.1
    ✔ rustc: 1.80.1 (3f5fd8dd4 2024-08-06)
    ✔ cargo: 1.80.1 (376290515 2024-07-16)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-x86_64-unknown-linux-gnu (default)
    - node: 22.3.0
    - npm: 10.8.2
    - bun: 1.0.22

[-] Packages
    - tauri [RUST]: 1.7.1
    - tauri-build [RUST]: 1.5.3
    - wry [RUST]: 0.24.10
    - tao [RUST]: 0.16.9
    - @tauri-apps/api : not installed!
    - @tauri-apps/cli [NPM]: 1.6.0

[-] App
    - build-type: bundle
    - CSP: unset
    - distDir: ../src
    - devPath: ../src

Stack trace

No response

Additional context

No response

[naman-crabnebula]

Hi!

I guess it is already fixed in Arch Linux + X11 + Cinnamon at least. I can run Tauri applications fine without WEBKIT_DISABLE_COMPOSITING_MODE. Can you check it yourself?