[ bug ] The application AppImage is so slow

[7system7]

Describe the bug
Actually the application gui is beautiful. But it is sooo slow. (at least on my system). It lags during scroll and have a big latency to react on any click. In a process explorer it perfectly visible that the application would like to burn the CPU w/o any reason. 😞

To Reproduce
Steps to reproduce the behavior:

1. Download AppImage
2. chmod +x on AppImage
3. Run it w/ much hope

Expected behavior
Running smoothly.

Screenshots

(In a regular laptop (w/ 8 cores) it is working on every core, and the the whole CPU is on 80-90%.)
On my desktop:

Desktop (please complete the following information):

• OS:

$ neofetch                                                                                                                                                                                                                                                               
                  -`                    system7@AMANDA 
                 .o+`                   -------------- 
                `ooo/                   OS: Arch Linux x86_64 
               `+oooo:                  Kernel: 6.6.10-arch1-1 
              `+oooooo:                 Uptime: 16 hours, 46 mins 
              -+oooooo+:                Packages: 1745 (pacman), 28 (flatpak) 
            `/:-:++oooo+:               Shell: bash 5.2.21 
           `/++++/+++++++:              Resolution: 2560x1080 
          `/++++++++++++++:             DE: GNOME 45.3 
         `/+++ooooooooooooo/`           WM: Mutter 
        ./ooosssso++osssssso+`          WM Theme: Adwaita 
       .oossssso-````/ossssss+`         Theme: adw-gtk3 [GTK2/3] 
      -osssssso.      :ssssssso.        Icons: Papirus [GTK2/3] 
     :osssssss/        osssso+++.       Terminal: guake 
    /ossssssss/        +ssssooo/-       CPU: 13th Gen Intel i9-13900K (32) @ 5.500GHz 
  `/ossssso+/:-        -:/+osssso+-     GPU: AMD ATI Radeon RX 6600/6600 XT/6600M 
 `+sso+:-`                 `.-/+oso:    Memory: 16475MiB / 63601MiB 
`++:.                           `-/+/
.`                                 `/                           
                                                                

• Browser: I would run it as a native app, but my main browser is Firefox 121.0.1 (64-bit)
• Version: v0.0.3-dev

Additional context

Terminal logs:

$ ./jelly-player_0.0.3-dev_amd64.AppImage                                                                                                                                                                                                                                
[2024-01-11][12:49:21][DEBUG][tiny_http] Server listening on [::1]:24718
[2024-01-11][12:49:21][DEBUG][tiny_http] Running accept thread
[2024-01-11][12:49:21][DEBUG][reqwest::connect] starting new connection: https://raw.githack.com/
[2024-01-11][12:49:21][DEBUG][reqwest::connect] starting new connection: http://192.168.88.2:8096/
[2024-01-11][12:49:22][DEBUG][reqwest::connect] starting new connection: http://192.168.88.2:8096/
[2024-01-11][12:49:22][DEBUG][reqwest::connect] starting new connection: http://192.168.88.2:8096/
[2024-01-11][12:49:22][DEBUG][reqwest::connect] starting new connection: http://192.168.88.2:8096/
[2024-01-11][12:49:22][DEBUG][reqwest::connect] starting new connection: http://192.168.88.2:8096/
[2024-01-11][12:49:22][DEBUG][reqwest::connect] starting new connection: http://192.168.88.2:8096/
[2024-01-11][12:49:22][DEBUG][reqwest::connect] starting new connection: http://192.168.88.2:8096/
[2024-01-11][12:49:22][DEBUG][reqwest::connect] starting new connection: http://192.168.88.2:8096/
[2024-01-11][12:49:22][DEBUG][reqwest::connect] starting new connection: http://192.168.88.2:8096/
[2024-01-11][12:49:22][DEBUG][reqwest::connect] starting new connection: http://192.168.88.2:8096/
[2024-01-11][12:49:22][DEBUG][reqwest::connect] starting new connection: http://192.168.88.2:8096/
[2024-01-11][12:49:22][DEBUG][reqwest::connect] starting new connection: http://192.168.88.2:8096/
[2024-01-11][12:49:22][DEBUG][reqwest::connect] starting new connection: http://192.168.88.2:8096/
[2024-01-11][12:49:22][DEBUG][reqwest::connect] starting new connection: http://192.168.88.2:8096/

[prayag17]

This is related to Tauri itself, the webkitgtk4 it uses for linux has terrible performance, it is directly an issue with JellyPlayer itself. Tho I do admit there are some performance issues with JP itself and I aam working on it.

tauri-apps/wry#890

[alanorth]

Interesting to know the cause. I come to check JellyPlayer progress every few weeks and find it causes high load on my Linux system and is unusable. Shame...

[prayag17]

You can try to build it on your system with the updated webkitgtk 4.0 installed

[alanorth]

I don't know how the versioning for webkitgtk works. I have these on my Arch Linux host:

• webkit2gtk 2.44.0-1
• webkitgtk-6.0 2.44.0-1

A post on the WebKitGTK blog talks about GTK 4 support in version 2.40, so presumably this is a version that should be high enough. Unless the underlying upstream issue with fetch() performance being slow still exists.

Update: I found this recent blog post detailing the WebKitGTK 2.44 release and apparently GTK 4 is the default now, so we shouldn't need to do anything. Unfortunately JellyPlayer still pegs all CPUs at 100% when I load it, and the interface is completely unusable. :\