[Bug 59528] New: Fade In Pro: Crashes immediately after splash screen

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=59528

            Bug ID: 59528
           Summary: Fade In Pro: Crashes immediately after splash screen
           Product: Wine
           Version: 10.14
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

Created attachment 80561
  --> http://bugs.winehq.org/attachment.cgi?id=80561
Backtrace collected by WinDbg

Fade In Pro for Windows v5.0.10 (requires license, demo version available at
https://www.fadeinpro.com/page.pl?content=download) crashes immediately after
the splash screen loads, triggering a WinDbg trace.

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

[Bug 59528] Fade In Pro: Crashes immediately after splash screen

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=59528

Hans Leidekker <[e-mail]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|-unknown                    |winhttp

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

[Bug 59528] Fade In Pro: Crashes immediately after splash screen

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=59528

--- Comment #1 from Hans Leidekker <[e-mail]> ---
The app sends a POST request in async mode and then writes the post data while
handling the SENDREQUEST_COMPLETE callback. This works but then it proceeds to
call WinHttpReceiveResponse() still on the same thread and we queue it because
we're in async mode. The app doesn't expect that because it proceeds to call
WinHttpQueryHeaders() to get the response status and content length. It doesn't
check the return value and calls WinHttpReadData() next which ends up crashing
because the response hasn't been received yet.

Receiving the response synchronously fixes it.

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