wails: Application soft crashes when using vue-virtual-scroller on Linux

Description

In my frontend I make use of the vue-virtual-scroller. This works fine in the dev view at localhost:34115 and on a Windows build. However when rendering this component on a Linux build it crashes the instance rendering a grey screen and hanging the inspector window.

To Reproduce

  1. Create a new wails instance with wails init -n myproject -t vue-ts
  2. Add the vue-virtual-scroller component
  3. Create Linux build (wails build -tags webkit2_41)
  4. Observe behaviour while rendering

Expected behaviour

The component to be rendered correctly on Linux just like on Windows.

Screenshots

No response

Attempted Fixes

As my system runs on Ubuntu 24.04 I added -tags webkit2_41 to the build and dev commands to get it to run (semi) properly. Additionally due to this bug I added WEBKIT_DISABLE_DMABUF_RENDERER=1 to the calls.

Both of these might affect how the result is displayed, however there is no logging indicating a crash and the window is still up and running. To further investigate this issue it would be nice to be able to take a look at the output of webkit (if that is something that exists).

System Details

# Wails
Version         | v2.9.2
Package Manager | apt   

# System
┌──────────────────────────────────────────────────────────────────────────┐
| OS           | Ubuntu                                                    |
| Version      | 24.04                                                     |
| ID           | ubuntu                                                    |
| Go Version   | go1.23.2                                                  |
| Platform     | linux                                                     |
| Architecture | amd64                                                     |
| CPU          | 12th Gen Intel(R) Core(TM) i7-12700                       |
| GPU 1        | Unknown                                                   |
| GPU 2        | AlderLake-S GT1 (Intel Corporation) - Driver: i915        |
| GPU 3        | GA104GL [RTX A4000] (NVIDIA Corporation) - Driver: nvidia |
| Memory       | 31GB                                                      |
└──────────────────────────────────────────────────────────────────────────┘

# Dependencies
┌───────────────────────────────────────────────────────────────┐
| Dependency | Package Name    | Status    | Version            |
| *docker    | docker.io       | Installed | 27.3.1             |
| gcc        | build-essential | Installed | 12.10ubuntu1       |
| libgtk-3   | libgtk-3-dev    | Installed | 3.24.41-4ubuntu1.2 |
| libwebkit  | Unknown         | Not Found |                    |
| npm        | npm             | Installed | 10.9.0             |
| *nsis      | nsis            | Available | 3.09-4ubuntu1      |
| pkg-config | pkg-config      | Installed | 1.8.1              |
└─────────────────── * - Optional Dependency ───────────────────┘

Additional context

No response

About this issue

  • Original URL
  • State: open
  • Created 2 years ago
  • Comments: 19 (8 by maintainers)

Most upvoted comments

I suspect these might be two different issues. My issue seems to stem from the libwebkit2gtk 4.1 version/bindings that crash the window and application (as shown in the segvault output). The issue from @lyimmi and @rainu seem to have very different behavior where the window and backend stay up but the frontend stops working.

I think it would be better if we also addressed these as separate issues.

Hi, I ran into this issue as well.

This started for me as of mid-december, my programs started “freezing” after around 2-3 days of uptime. I use VUE with very few plugins, that can be an issue. (vue3.x, vue-router, vue-i18n, gsap)

Reloading the window does not help, the webkitwebprocess slowly but surely gobbling up memory. In my case GPU policy does not matter.

Around that time frame there was an update for libwebkit2gtk. I’m in the process of finding the last “good” version of the package, but for me the issue only presents it self after a longer uptime and when users are actively working with the program, so it is a slow and annoying process.

My current libwebkit version is: libwebkit2gtk-4.0-37 (2.46.5-0ubuntu0.22.04.1) From my releases and the dpkg history I’m suspecting it broke somewhere around december 10th.

I have to rollback and test at-least the following versions:

  • libwebkit2gtk-4.0-37:amd64 (2.44.3-0ubuntu0.22.04.1)
  • libwebkit2gtk-4.0-37:amd64 (2.46.1-0ubuntu0.22.04.1)
  • libwebkit2gtk-4.0-37:amd64 (2.46.4-0ubuntu0.22.04.1)

@ysmilda could you try rolling back to an older version of libwebkit2gtk-4.0 and try your test with that?

edit: As @rainu described, the window and the backend works fine, just the webview stops rendering, or does it very slowly / randomly.