Crash on plugin removal or exiting DAW

[mister-benjamin]

I can successfully insert and use Fabfilter ProQ 3 on a channel strip of Harrison Mixbus. But when I want to remove the plugin or exit Mixbus, the Airwave wine process crashes and freezes the DAW.

I used AirwaveManager 1.3.3 installed from the dpkg provided on this site. I am on Debian 10 amd64. Wine version is 4.0 64-bit from the official Debian repo. My plugin host is Harrison Mixbus 32C 6.0.

Here's the backtrace:
backtrace.txt

After disabling 2D graphics rendering in Mixbus, the backtrace shows some more human readable information:
backtrace2.txt

[asb2m10]

If it happens when you open multiple airwave plugins, I would suggest to try my branch to see if you have still an issue: https://github.com/asb2m10/airwave

The problem is related to the signal handler and I've removed it since it is not required anymore with Renoise.

[KottV]

@asb2m10 Hi, what wine version do you use?
I'm unable to run any plugin with recent Wine 5.2

Unhandled exception: page fault on read access to 0x00000060 in 64-bit code (0x0000000180001efd).

[mister-benjamin]

If it happens when you open multiple airwave plugins, I would suggest to try my branch to see if you have still an issue: https://github.com/asb2m10/airwave

The problem is related to the signal handler and I've removed it since it is not required anymore with Renoise.

Thanks for bringing your fork to my attention. I compiled it in order to see if it solves my problem. Unfortunately using the manual build failed to successfully scan my plugin. I am now using LinVST which seems to work for me, so I didn't try to investigate this any further.

@asb2m10 Hi, what wine version do you use?
I'm unable to run any plugin with recent Wine 5.2

Unhandled exception: page fault on read access to 0x00000060 in 64-bit code (0x0000000180001efd).

I am using Wine 4.0 (Debian 4.0-2).

[asb2m10]

@asb2m10 Hi, what wine version do you use?
I'm unable to run any plugin with recent Wine 5.2

Unhandled exception: page fault on read access to 0x00000060 in 64-bit code (0x0000000180001efd).

I'm using Wine 5.2. I've tested Pro-Q 3 on my side and it worked fine.

If you build it in debug with my branch, there should be more details on the stacktrace when the plugin crash.

[KottV]

Run with debug build. Can it help?

out.txt

[asb2m10]

The plugin crashed on first call... usually this means a wine build issue or not.

1. Put the plugin log level in flood mode (with the airwave-manager). Then open the plugin while leaving the airwave-manager open so you can see the logs from airwave-manager.

2. Wine could log the issue but there is almost no way to see it. To see this change the file /opt/airwave/bin/airwave-host-64.exe at the end from

# and try to start the app
exec "$WINELOADER" "$apppath" "$@"

to

export WINEDEBUG=fixme-all,warn,trace+thread

# and try to start the app
exec "$WINELOADER" "$apppath" "$@" >> /tmp/airwave.log 2>&1

I hope that /tmp/airwave.log will have a better description on what is going on...

[KottV]

Sorry for long no answering, but I've stuck with building recent Carla. When I resolve that issue - I'll post the results.

[asb2m10]

No problem. If you pull from my latest branch, I've added a tester that logs wine logs on
the command line.

$ export WINEDEBUG=fixme-all,warn+all
$ /opt/airwave/bin/airwave-tester '~/.vst/DUNE 3.so'

[KottV]

Thanks.
I see same backtrace only. Did I missed smth?

out.txt