You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TL;DR: this appears to be the same problem as #47, i.e. FlexASIO is being linked against an already-loaded foreign PortAudio DLL instead of the PortAudio DLL that is bundled with FlexASIO; that foreign DLL has ASIO support built-in, resulting in FlexASIO and PortAudio re-entering itself upon initialization. Hilarity ensues in the form of infinite recursion.
We need to understand why the fix for #47, i.e. b5a24c8, doesn't seem to work in this case.
The text was updated successfully, but these errors were encountered:
I am able to reproduce on a fresh Windows 11 install, Mixxx 2.3.3, and FlexASIO 1.9.
The root cause is somewhat silly: the reason why b5a24c8 doesn't work anymore is because it's including portaudio_x86.dll and portaudio_x64.dll in the manifest, but the PortAudio DLL changed in the mean time, most likely as a side effect of PortAudio/portaudio@242a024 (first included in FlexASIO 1.8) - it's now called portaudio.dll. As a result the manifest has no effect, thus resurrecting #47.
dechamps
changed the title
Mixxx crashes when FlexASIO is installed due to re-entering into PortAudio on initialization
Mixxx crashes on startup when FlexASIO is installed
Feb 2, 2023
This is fixed in FlexASIO 1.10, which ships with a manifest that ensures the Windows DLL loader will not share FlexASIO's portaudio.dll with any other part of the host application.
See mixxxdj/mixxx#10081, PortAudio/portaudio#766.
TL;DR: this appears to be the same problem as #47, i.e. FlexASIO is being linked against an already-loaded foreign PortAudio DLL instead of the PortAudio DLL that is bundled with FlexASIO; that foreign DLL has ASIO support built-in, resulting in FlexASIO and PortAudio re-entering itself upon initialization. Hilarity ensues in the form of infinite recursion.
We need to understand why the fix for #47, i.e. b5a24c8, doesn't seem to work in this case.
The text was updated successfully, but these errors were encountered: