[Bug 45269] FL Studio 20.0.0.445: Odd problem possibly indicative of WINE file-descriptor problem

[wine-bugs at winehq.org]

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

--- Comment #9 from Michael Nelson <iam at mcnster.com> ---
(In reply to ajduck from comment #7)
> Funny, I also discovered this exact same behavior yesterday independently. I
> was going to report it here but you beat me to it! (Already submitted
> workaround on AppDB).
> 
> This is what I used to work around the issue:
> 
> $ wine FL64.exe > fl-winedebug.log 2> fl-winedebugerr.log
> 
> (both going to /dev/null also works)
> 
> As was found here, I found that logging only one of stdout or stderr (not
> both at the same time) didn't preventing the hanging. It's weird indeed.
> 
> Additional notes:
> - There's no FL Studio 19, FL Studio 12 was the previous version, they
> skipped to FL Studio 20 after FL Studio 12 to celebrate the program's 20th
> anniversary.
> - FL Studio 12 doesn't have this problem on Wine 3.9. It's only FL Studio 20.
> - This behavior started happening after one of the FL Studio 20 betas
> (12.1+), the version I remember trying was FL Studio 12.4 beta.
> - The "RtlpWaitForCriticalSection" hanging that FL Studio 20 gets on start
> up (the hanging described here) also is the same hanging that happens when
> trying to use the bit-bridging functionality. I reported this a few months
> ago at #44827.
> 
> Running with Wine 3.9 (devel) on elementary OS 0.4 Loki (based on Ubuntu
> 16.04).
> 
> (regarding #44827, I actually wonder what would happen if we could somehow
> get FL Studio to run ilbridge.exe with > and 2> as well when trying to
> bit-bridge VST plugins)

It is weird indeed (I'm glad someone has reported the same problem and I'm not
losing my mind...).

Also I stand corrected.  FL 20 was preceeded by FL 12.

-- 
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.