[Bug 42502] New: SlingPlayer 1.5.1 crashes on load (Assertion failure)

[wine-bugs at winehq.org]

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

            Bug ID: 42502
           Summary: SlingPlayer 1.5.1 crashes on load (Assertion failure)
           Product: Wine
           Version: 2.2
          Hardware: x86
               URL: http://download.slingmedia.com/player/pc/SlingPlayer-S
                    etup-EU-1.5.1.343.exe
                OS: Linux
            Status: NEW
          Keywords: download, regression
          Severity: normal
          Priority: P2
         Component: directx-d3d
          Assignee: wine-bugs at winehq.org
          Reporter: imwellcushtymelike at gmail.com
                CC: stefan at codeweavers.com
            Blocks: 17972, 18010, 31651, 38938
   Regression SHA1: 34d8b987c493544f640bf5ca0a5a6cbb3d3f4e7b
      Distribution: Ubuntu

Created attachment 57376
  --> https://bugs.winehq.org/attachment.cgi?id=57376
Wine 2.1 console output

SlingPlayer 1.5.1 crashes around 98% of the time with an assertion failure, 1%
of the time with a page fault, and 1% of the time it loads, but crashes later
in a similar manner. The attached log shows an assertion failure, though the
debugger doesn't run.

wine: Assertion failed at address 0xb77df428 (thread 0009), starting
debugger...
*** Error in `/home/test/.wine/drive_c/Program Files/Sling
Media/SlingPlayer/SlingPlayer.exe': corrupted double-linked list: 0x7c3ba500
***

This is a regression.

34d8b987c493544f640bf5ca0a5a6cbb3d3f4e7b is the first bad commit
commit 34d8b987c493544f640bf5ca0a5a6cbb3d3f4e7b
Author: Stefan Dösinger <stefan at codeweavers.com>
Date:   Thu Jul 30 18:50:15 2015 +0200

    wined3d: Try to detect the polygon offset scale value.

    FEAR draws the same geometry twice, the second time using zfunc=equal.
    In both cases it sets a huge depth bias of -0.5, presumably to get
    better precision for the fragile Z comparison. The GL polygon offset we
    set ends up being so large that it pulls the geometry into the negative
    Z range. It isn't clipped (or no longer, older NV drivers probably had a
    separate bug there), but the Z value gets clamped to 0.0 in the first
    draw and doesn't match the incoming Z in the second draw.

This commit cannot be automatically reverted in latest git.
No known workaround.

The crash is avoided by running it under Valgrind.

Optional native gdiplus to work around Bug 30899.

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