Reaper crashing

[MatiM72737]

Thanks for giving yabridge a shot!

• I read through both the troubleshooting and the known issues sections, and my issue wasn't listed there

Problem description

i'm using hyprland on arch and reaper is randomly crashing when i'm loading plugins with yabridge, on kde all was working fine, but there was lot of packages downloaded so i don't know that's wrong, I'm using wine-staging 9.20, tried 9.21 too

What did you expect to happen?

Reaper load properly

What actually happened?

Randomly crash

Operating system

Arch

How did you install yabridge?

aur

yabridge version

5.1.1-2

yabridgectl version

5.1.1-2

Wine version

stagging 9.20

Plugin

doesn't matter

Plugin type

both VST2 and VST3

Plugin architecture

64-bit

Host

Reaper

Desktop environment or WM

hyprland

GPU model

gtx 970

GPU drivers and kernel

575.57.08-5 6.15.2-arch1-1

Debug log

No response

Anything else?

No response

[pasteluengas]

this happens to me, but apparently only with 32 bit plugins.
console says

[Wine STDERR] wine: failed to start L"Z:\\usr\\bin\\yabridge-host-32.exe.so"

the file exists, but...
1- if you cat it, you'll see its not a windows executable file, its a shell script (same as the 64 bit .exe so im not sure if this is causing the problem)
2- both nano /usr/bin/yabridge-host-32.exe and nano /usr/bin/yabridge-host.exe have exactly the same content

[plaimbock]

Maybe try to install the latest stable yabridge release from https://github.com/robbert-vdh/yabridge/releases/download/5.1.1/yabridge-5.1.1.tar.gz
Next do not forget to run yabridgectl sync
And see if it helps?

[pasteluengas]

i solved it a couple of days ago by downgrading wine-staging to 9.21

[untilde]

I'm also having this weird issue when loading plugins on Reaper, even 64 bits ones.

Fedora KDE Plasma 42, Ryzen 5 3600, 16gb ram, rx 6600 8gb...

The thing is: I've tried debugging it several different ways to no clue...

The window simply hangs, the GUI doesn't load, I just get the empty/gray Reaper window, and it stays frozen forever, forcing me to close it.

Currently using wine staging version 9.21 and latest yabridge release, already did sync, tried a new wine prefix, installed corefonts and dxvk... I'm completely lost here.

The plugins that crash the most:
DMG Audio and Pulsar Audio.
They do work, but it's completely random if the UI will crash or not.

The issue seems related to VST3, since it never really happened to any VST2 instances.

[pasteluengas]

a few months something similar happened to me in Reaper, are you using wayland?

[untilde]

After lots of testing and swapping distros 3 times, my best guess is that DXVK is the main culprit for the crashes. I'm now using a separate prefix for DXVK plugins, and avoiding them as much as possible... I'm on Kubuntu 25.04 (Wayland), everything works fine, some rare crashes with the DXVK plugins only. The plugins in my regular prefix work fine.

[relaborn]

dxvk updated to 2.7 a few months ago and that version breaks some things, especially if your mesa is old. Try installing 2.6.

[untilde]

Already updated my mesa drivers and still getting a ton of crashes in DXVK.
I can already pinpoint DXVK as the cause, because using the same plugins in a prefix without DXVK never crash.
Despite being unable to interact with the UI without DXVK, I can still use the controls the DAW provide me. As long as you don't open the UI, they won't crash at all.
I'm just avoiding all these plugins for the best.

[jmckernon]

I think two issues are being crossposted here somewhat. One is an issue with the Arch package (maybe for other OSes, idk), whereby /usr/bin/yabridge-host-32.exe is a shell script, but the process is trying to open it as a dynamic library. I was afflicted by this and downgrading worked as a fix. I imagine this would be straightforward for someone with knowledge of the package to fix, but I don't know for certain. On the other hand, there's an issue relating to graphics, mesa, and DXVK as reported by untilde and others.

The causes of the two are not the same and it seems worthwhile for each to have its own bug report on here. Having said that, I don't know which the original bug report relates to so it's hard to say which ought to stay here and which ought to be moved to a new bug report.