modrinth
Linux-specific performance, graphical, or crashing issues [MEGA-ISSUE]
Please confirm the following.
- [x] I checked the existing issues for duplicate problems
- [x] I have tried resolving the issue using the support portal
- [x] I have ensured my Modrinth App installation is up to date
What version of the Modrinth App are you using?
0.9.0
What operating systems are you seeing the problem on?
Linux
Describe the bug
I use an Nvidia GPU and Arch Linux. The app just updated to 0.9.0, but immediately I noticed that it's unusably slow. When interacting with it, like moving the cursor from one button to another, it freezes for about a second, although animations look smooth afterwards (if I stop moving). I see no errors or logs anywhere. The GPU is relevant because, as with previous versions and even other apps, the app crashes on startup if run normally, so it needs the workaround of setting WEBKIT_DISABLE_DMABUF_RENDERER=1 (or WEBKIT_DISABLE_COMPOSITING_MODE=1), but that workaround worked decently in previous versions, so something changed now. The Modrinth app seems to account for software rendering by providing the "advanced rendering" toggle, but even though turning it off is supposed to help with this, it doesn't improve the situation.
I'm also facing this issue on Arch with version 0.9.0 (modrinth-app-bin, aur). Although, I don't have a NVIDIA GPU; rather, my system uses an Intel iGPU. I've tried turning off Advanced rendering, however it doesn't resolve the issue.
https://github.com/user-attachments/assets/a6eb2c10-8245-4213-88da-6884c88dffb7
I can reproduce this issue. Compiling from source and using this binary also doesn't help.
This issue is probably caused by WebKit - web view used by tauri on Linux. The tauri team is working on other alternatives like cef (chromium) or servo. For now we can only way and try to find bottlenecks and optimize them if we can.
I'm running Manjaro and after updating I now get this when I run version 0.9.0
Could not create default EGL display: EGL_BAD_PARAMETER. Aborting...
** (ModrinthApp:2121): WARNING **: 19:50:50.282: atk-bridge: get_device_events_reply: unknown signature
this is what i have tried and still getting
Could not create default EGL display: EGL_BAD_PARAMETER. Aborting...
** (ModrinthApp:12167): WARNING **: 20:49:54.234: atk-bridge: get_device_events_reply: unknown signature
I have a similar problem but with a AMD GPU, previous version seemed to run perfectly.
I have a similar problem but with a AMD GPU, previous version seemed to run perfectly.
Depending on how you installed it, you might be unintentionally still using the workaround I mentioned. For me, /usr/bin/modrinth-app is a shell script that sets WEBKIT_DISABLE_DMABUF_RENDERER=1 and runs the actual app executable in /opt/, presumably to prevent it from crashing for Nvidia users. Can you try running the app directly, or changing that variable to 0 instead of 1?
I have a similar problem but with a AMD GPU, previous version seemed to run perfectly.
Depending on how you installed it, you might be unintentionally still using the workaround I mentioned. For me, /usr/bin/modrinth-app is a shell script that sets WEBKIT_DISABLE_DMABUF_RENDERER=1 and runs the actual app executable in /opt/, presumably to prevent it from crashing for Nvidia users. Can you try running the app directly, or changing that variable to 0 instead of 1?
That fixes it for me, thanks.
Manually compiling and setting WEBKIT_DISABLE_DMABUF_RENDERER=0 completly fixes this issue for me.
That fixes it for me, thanks.
Welp, that confirms the idea that this is a problem for Nvidia+Linux users, since we can't change that to 0 or it will crash on startup
Arch users can try the modrinth-app-segfault-fix-bin AUR package for a quick fix, I've been using it myself ever since 0.8.0. Users on other distros can try setting these env variables:
export WEBKIT_DISABLE_DMABUF_RENDERER=1
export LIBGL_ALWAYS_SOFTWARE=1
export GDK_BACKEND=x11
I am also having this issue (on pop os with Nvidia gpu), hope this gets fixed soon.
Manually compiling and setting
WEBKIT_DISABLE_DMABUF_RENDERER=0completly fixes this issue for me.
Is this something we can edit in GH actions to generate a working build?
Manually compiling and setting
WEBKIT_DISABLE_DMABUF_RENDERER=0completly fixes this issue for me.Is this something we can edit in GH actions to generate a working build?
Unfortunately, if you missed this detail, setting that makes the app crash on startup on Nvidia. To be clear, that variable was always set to 1 by default as a workaround for Nvidia users, but the issue is that 0.9 lags when it's set. (Unless I'm missing something about what Norbiros did)
I've run a bisect and c39bb78e38cb9cfe13f01f4a9bee277881b52efb is the main commit that introduced the issue. Previous commits already ran very poorly but were usable. That commit is really massive, though.
My issue is not the same, but it is because of a default flag set, which fixes the black screen issue, but introduces lagging. The main executable in /opt/modrinth-app/modrinth-app launches without issue, does not lag and uses my gpu. However, the default /usr/bin/modrinth-app, runs the main executable with WEBKIT_DISABLE_DMABUF_RENDERER=1. Removing that flag, the app does not lag anymore. This is not the only issue, it fixes, but now the logs dont crash the app anymore. However, my friend has the same black screen issue now, so this is not the best fix.
I have an amd integrated gpu, and i am on arch using the modrinth-app-bin package from AUR
The app is completely unusable for me.
I have an nvidia-gpu and version 0.9.2. I am on arch.
The app crashes without WEBKIT_DISABLE_DMABUF_RENDERER=1 and GDK_BACKEND=x11.
LIBGL_ALWAYS_SOFTWARE does not matter.
env WEBKIT_DISABLE_DMABUF_RENDERER=1 LIBGL_ALWAYS_SOFTWARE=0 GDK_BACKEND=x11 /opt/modrinth-app/modrinth-app "$@"
I compiled it from source, used the modrinth-app, modrinth-app-bin and modrinth-app-segfault-fix-bin. All exhibit the issue.
Same issue here. Very hard to use on POP OS PC with NVIDIA GPU. Zero lagg on the same OS on my laptop without GPU.
Just installed it for the first time, didn't work. I'm using arch on hyprland with a nvidia card as well.
This is what terminal prints:
❯ modrinth-app
(modrinth-app:803815): Gtk-WARNING **: 21:02:32.228: Theme parsing error: gtk-dark.css:6691:68: Invalid name of pseudo-class
(WebKitWebProcess:803846): Gtk-WARNING **: 21:02:32.434: Theme parsing error: gtk-dark.css:6691:68: Invalid name of pseudo-class
/usr/bin/modrinth-app: line 2: 803815 Segmentation fault (core dumped) env WEBKIT_DISABLE_DMABUF_RENDERER=1 /opt/modrinth-app/modrinth-app "$@"
Arch Linux, Nvidia/AMD. The app is extremely slow, even though it should run on my iGPU. It also crashes very often
Having the same issue on nvidia sadly, app runs at 0,7fps when moving mouse to different hover objects
Use a 4060, same issue, thought my processed died already after seeing the horrendous fps and tried various packages on arch, still same behavior. the one with the segfault fix gives os error about perms
Also having this issue on debian 12, with deb, appimage and flatpak... I know a big part of this issue is with webkit / tauri, and that they're planning to move to probs CEF, but from what I know theres no planned/soon release for that... it would be rly nice if there was an option to somehow make app use less animations or something (whatevers causing the fps drop) to return it to the performance it had before. I have no idea if thats possible, tho. Cause yeah, app is unusable right now. :/
I will try just downgrading the app. I didn't notice any functional changes, not anything I need for sure, so I hope it'll go well
