[Bug 44827] FL Studio: Soft locks forever when attempting to "bit bridge" a 32-bit/64-bit VST plugin

[wine-bugs at winehq.org]

https://bugs.winehq.org/show_bug.cgi?id=44827

--- Comment #3 from ajduck at outlook.com ---
Still happens as of Wine 4.4 Staging.

--------

Some additional info:

There are two ilbridge.exe executables, one for 32-bit and one for 64-bit.
Here's an example of what processes (+ options) are running when bit-bridging
is attempted:

For FL Studio 32-bit:

    C:\Program Files (x86)\Image-Line\FL Studio 20\FL.exe
    C:\Program Files (x86)\Image-Line\FL Studio
20\System\Tools\Bridge\64bit\ilbridge.exe -wrapper -address
{73DA306F-6855-4F59-B63E-ADF54D47013B}1 -processid 52 -dpiaware

For FL Studio 64-bit:

    C:\Program Files (x86)\Image-Line\FL Studio 20\FL64.exe
    C:\Program Files (x86)\Image-Line\FL Studio
20\System\Tools\Bridge\32bit\ilbridge.exe -wrapper -address
{888E87B6-9C3E-4851-9CE8-C3252E9D11A3}1 -processid 54 -dpiaware

As you can probably see, the 32-bit version of FL uses the ilbridge.exe
executable in the 64bit folder (to bridge a 64-bit plugin), and vice-versa for
64-bit FL. An address and process id is passed as options into the bridging
executable.

As mentioned in the OP, it waits for something and keeps eventually timing out:

    0048:err:ntdll:RtlpWaitForCriticalSection section 0x17e8b20 "?" wait timed
out in thread 0048, blocked by 0035, retrying (60 sec)

--------

I ran FL64.exe with WINEDEBUG='+relay,+tid' and got it down to a 15MB log:
https://aljelly.keybase.pub/linux%20related/fl64-bridging-32bit-wine-filtered.log

(I strongly recommend right-clicking the link, select "Save Link As..." and
then looking at the file through less.)

To cut the log down in size I cut everything out before the first occurrence of
CrossOver.dll (the 32-bit VST I'm trying to bridge), and filtered out any lines
with 'gdi32', 'user32', 'winex11', or 'window proc' in them (because I *think*
most of those are just GUI related).

A lot of the file might be irrelevant to the issue however (the lines to do
with fonts are very likely so). Some of it might be due to unrelated .NET
Framework services running in the background. Line 743 has the wait timed out
error message.

Probably strings of relevance to search for are: "CrossOver" or
"CrossOver.dll", "0037" and "004a" (thread ids related to the bridging
attempt), "Wrapper" or "Wrapper says", "ilbridge.exe", and
"{E682D1D3-5CF7-4213-B873-D426EF623DCB}".

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.