[Bug 45269] New: FL Studio 20.0.0.445: Odd problem possibly indicative of WINE file-descriptor problem
https://bugs.winehq.org/show_bug.cgi?id=45269 Bug ID: 45269 Summary: FL Studio 20.0.0.445: Odd problem possibly indicative of WINE file-descriptor problem Product: Wine Version: 3.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: iam(a)mcnster.com Distribution: --- Howdy folks, I have install FL Studio 20 in a 64-bit wineprefix. When I run: $ wine64 .wine/drive_c/Program\ Files\ \(x86\)/Image-Line/FL\ Studio\ 20/FL64.exe ... I receive the following diagnostics which repeats the last line every 60 seconds, forever: 0009:fixme:explorerframe:taskbar_list_SetProgressState iface 0x37bc620, hwnd 0x20126, flags 2 stub! 003e:err:ntdll:RtlpWaitForCriticalSection section 0x1c6d470 "?" wait timed out in thread 003e, blocked by 0009, retrying (60 sec) 003e:err:ntdll:RtlpWaitForCriticalSection section 0x1c6d470 "?" wait timed out in thread 003e, blocked by 0009, retrying (60 sec) YET! When I run: $ wine64 [path-to-FL64.exe] 2>&1 | tee run.log ... the program runs as expected with no errors or hang. Weird, huh? Two facts to consider, unfortunately: 1) FL Studio 19 worked flawlessly under wine-staging-3.7, and I don't remember if FL Studio 19 or 20 worked under wine-staging-3.8, but one of them DIDN'T. Any help would be appreciated. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45269 --- Comment #1 from Michael Nelson <iam(a)mcnster.com> --- Additional info: The problem occurs under wine-staging-3.9 on the Gentoo distribution. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45269 --- Comment #2 from Michael Nelson <iam(a)mcnster.com> --- More additional info: - The problem also occurs under wine-vanilla-3.9/gentoo. - I would attach a complete WINE log of the failure, but it seems that when I redirect stderr to stdout via `> bug.log 2>&1', the programs runs correctly as expected! So I am at a loss as to how to capture the output stream with the diagnostics.... -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45269 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12(a)gmail.com --- Comment #3 from Zebediah Figura <z.figura12(a)gmail.com> --- Does the problem occur if you just redirect either stdout or stderr? I.e. does something like 'wine FL64.exe 2>stderr.log' work? -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45269 --- Comment #4 from Michael Nelson <iam(a)mcnster.com> --- Created attachment 61514 --> https://bugs.winehq.org/attachment.cgi?id=61514 Log with no redirections. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45269 --- Comment #5 from Michael Nelson <iam(a)mcnster.com> --- (In reply to Zebediah Figura from comment #3)
Does the problem occur if you just redirect either stdout or stderr? I.e. does something like 'wine FL64.exe 2>stderr.log' work?
Hope this helps. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45269 --- Comment #6 from Michael Nelson <iam(a)mcnster.com> --- (In reply to Zebediah Figura from comment #3)
Does the problem occur if you just redirect either stdout or stderr? I.e. does something like 'wine FL64.exe 2>stderr.log' work?
Whups. Bugzilla hosed my reply. 1. The problem occurs when I redirect stdout to file. 2. The problem occurs when I redirect stderr to file. (Log attached above.) 3. The problem does NOT occur when I redirect stderr into stdout to file. -= M =- -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45269 ajduck(a)outlook.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ajduck(a)outlook.com --- Comment #7 from ajduck(a)outlook.com --- 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) -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45269 --- Comment #8 from ajduck(a)outlook.com --- *prevent Also, link to the bug I was referencing: bug #44827 (also, add "download" to Keywords?) -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45269 --- Comment #9 from Michael Nelson <iam(a)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.
https://bugs.winehq.org/show_bug.cgi?id=45269 Michael Nelson <iam(a)mcnster.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTOURBUG --- Comment #10 from Michael Nelson <iam(a)mcnster.com> --- I did some regression testing and it looks like the experimental .dll.so I was testing is causing the problem. Sorry to have wasted anyone's time. I will mark this bug resolved. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45269 Józef Kucia <joseph.kucia(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|NOTOURBUG |INVALID CC| |joseph.kucia(a)gmail.com -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45269 André H. <nerv(a)dawncrow.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nerv(a)dawncrow.de Status|RESOLVED |CLOSED --- Comment #11 from André H. <nerv(a)dawncrow.de> --- closing invalid -- 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.
https://bugs.winehq.org/show_bug.cgi?id=45269 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|FL Studio 20.0.0.445: Odd |FL Studio 20: Odd problem |problem possibly indicative |possibly indicative of WINE |of WINE file-descriptor |file-descriptor problem |problem | URL| |https://web.archive.org/web | |/20180930122250/http://demo | |download.image-line.com/fls | |tudio/flstudio_win_20.0.5.6 | |74.exe CC| |focht(a)gmx.net Severity|major |normal Keywords| |download -- 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.
participants (2)
-
wine-bugs＠winehq.org -
WineHQ Bugzilla