[Bug 49260] Notation Composer 4 (MFC app) freezes in CPropertySheet::DoModal on Mac OS X

[WineHQ Bugzilla]

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

Anastasius Focht <focht at gmx.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                URL|                            |https://web.archive.org/web
                   |                            |/20200527180818/https://www
                   |                            |.notation.com/DownloadTrial
                   |                            |Product.php?Trial_Product=C
                   |                            |omposer_English
            Summary|Some MFC applications using |Notation Composer 4 (MFC
                   |CPropertySheet freeze in    |app) freezes in
                   |CPropertySheet::DoModal on  |CPropertySheet::DoModal on
                   |Mac OS X                    |Mac OS X
           Keywords|                            |download

--- Comment #3 from Anastasius Focht <focht at gmx.net> ---
Hello Reinhold,

the app 'Notation Composer 4' works well here on Linux. No freeze in property
sheet dialog on any of the steps you've provided. I've tested with Wine 5.7,
5.9 and from current master HEAD (wine-5.9-67-g8257fe88fb). It might be an Mac
OS X specific thing here.

The app seems to be Wine aware:

--- snip ---
$ pwd
/home/focht/.wine/drive_c/Program Files/Notation_4/Composer_4

$ WINEDEBUG=+seh,+relay,+win,+msg,+propsheet wine ./Composer.exe >>log.txt 2>&1
...
030c:Call KERNEL32.GetProcAddress(7bc20000,1409bf868 "wine_get_version")
ret=140086b5d
030c:Ret  KERNEL32.GetProcAddress() retval=7bc34dfc ret=140086b5d
030c:Call KERNEL32.GetProcAddress(7bc20000,1409bf850 "wine_get_build_id")
ret=140086b70
030c:Ret  KERNEL32.GetProcAddress() retval=7bc34e14 ret=140086b70
030c:Call KERNEL32.GetProcAddress(7bc20000,1409bf838 "wine_get_host_version")
ret=140086b83
030c:Ret  KERNEL32.GetProcAddress() retval=7bc34e2c ret=140086b83
030c:Call ntdll.wine_get_version() ret=140086ba3
030c:Ret  ntdll.wine_get_version() retval=7f20492c8714 ret=140086ba3
030c:Call ntdll.wine_get_build_id() ret=140086ba9
030c:Ret  ntdll.wine_get_build_id() retval=7f20492c8dc0 ret=140086ba9
030c:Call ntdll.wine_get_host_version(0607f358,0607f360) ret=140086bb8
030c:Ret  ntdll.wine_get_host_version() retval=7f20492cce42 ret=140086bb8 
...
--- snip ---

>From a cursory view it uses the Wine detection for logging/diagnostic purpose
only but I might be wrong. I've seen vendors putting Wine-specific handling in
their application code which in some cases makes things worse because Wine
evolves as well. See bug 42497 for such example (broken
'user32.UpdateLayeredWindow' code paths).

Anyway, could you create a trace log using following command line and attach
the resulting log file to this ticket? At the time of the "freeze" just kill
the processes from another terminal using 'wineserver -k'.

--- snip ---
# cd to app dir

$ WINEDEBUG=+seh,+relay,+win,+msg,+propsheet wine ./Composer.exe >>log.txt 2>&1
--- snip ---

You might need to compress the text file before attaching. Alternatively
provide me with an external download link to the log (can be temporary).

I've created a snapshot via Internet Archive to "pin" the exact app version for
reproducing the issue. Just in case the vendor replaces the download with a
newer version (generated link / non-unique url).

https://web.archive.org/web/20200527180818/https://www.notation.com/DownloadTrialProduct.php?Trial_Product=Composer_English

$ sha1sum Inst_NS_Composer_4_English_Trial.msi 
7828103c644f658faf0407c9e068efe85169afcb  Inst_NS_Composer_4_English_Trial.msi

$ du -sh Inst_NS_Composer_4_English_Trial.msi 
24M    Inst_NS_Composer_4_English_Trial.msi

$ wine --version
wine-5.9-67-g8257fe88fb

Regards

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