[Bug 19474] New: Team Fortress 2 crashes on startup with an assertion failure

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

Summary: Team Fortress 2 crashes on startup with an assertion
                    failure
           Product: Wine
           Version: 1.1.26
          Platform: PC
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: directx-d3d
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]
                CC: [e-mail]

Created an attachment (id=22636)
 --> (http://bugs.winehq.org/attachment.cgi?id=22636)
Team Fortress 2 standard error log

With wine-1.1.26-231-gfe9d360 and NVIDIA driver version 185.18.14, launching
Team Fortress 2 leads to its immediate termination with:

err:d3d_surface:IWineD3DSurfaceImpl_ModifyLocation 0x1a0308: Surface does not
have any up to date location
err:d3d_surface:IWineD3DSurfaceImpl_ModifyLocation 0x1a0308: Surface does not
have any up to date location
utlmemory.h (322) : Assertion Failed: IsIdxValid(i)

Mysteriously, the utlmemory.h assertion message does not appear when
redirecting standard error to file. A regression test showed that the bad
commit was:

fb77678e9f1bc5e1baa20f241d2fc00a718496e3 is first bad commit
commit fb77678e9f1bc5e1baa20f241d2fc00a718496e3
Author: Henri Verbeet 
Date:   Fri Jul 24 10:44:14 2009 +0200

wined3d: Manage event queries in the context.

:040000 040000 0584e071412e6c4f9a1bfdf479e8692d42da4bdf
8f2af876abed8a743a03be7ba8a3e9114144e389 M    dlls

Team Fortress 2 does not crash with Wine from a prior commit.

[Bug 19474] Team Fortress 2 crashes on startup with an assertion failure

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

--- Comment #1 from Henri Verbeet   2009-07-27 05:00:50 ---
Works for me, but it probably also depends on your specific graphics settings,
and perhaps graphics card. Also note that 185.18.14 appears to break the ingame
HUD among other things in TF2 (I don't know if that's our bug or nvidia's, but
it works with 180.60).

The utlmemory.h assertion is generated by TF2, not Wine or the driver, so this
could also be a general memory corruption issue, not necessarily related to
that patch. There is one bug in the context management related to destroying a
context's current rendertarget which could cause random behaviour,
http://bugs2.winehq.org/attachment.cgi?id=22626 should fix that. You could try
that, but at first sight this looks different.

[Bug 19474] Team Fortress 2 crashes on startup with an assertion failure

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

--- Comment #2 from Andrew Nguyen   2009-07-27 05:31:12 ---
That patch does allow Team Fortress 2 to start successfully. Should I mark this
bug a duplicate of bug 19462?

[Bug 19474] Team Fortress 2 crashes on startup with an assertion failure

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

--- Comment #3 from Henri Verbeet   2009-07-27 05:52:00 ---
In that case, yeah.

[Bug 19474] Team Fortress 2 crashes on startup with an assertion failure

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

Andrew Nguyen  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |DUPLICATE

--- Comment #4 from Andrew Nguyen   2009-07-27 06:12:10 ---
This is a duplicate of bug 19462.

*** This bug has been marked as a duplicate of bug 19462 ***

[Bug 19474] Team Fortress 2 crashes on startup with an assertion failure

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

Andrew Nguyen  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #5 from Andrew Nguyen   2009-07-27 06:12:44 ---
Closing the bug.

[Bug 19474] Team Fortress 2 crashes on startup with an assertion failure

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

JP St. Pierre  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #6 from JP St. Pierre   2009-07-30 09:34:58 ---
*** Bug 19512 has been marked as a duplicate of this bug. ***