[Bug 47610] New: No Man' s Sky Crashes to Desktop after ~20 minutes starting with wine-4.11 ( Staging)

[wine-bugs at winehq.org]

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

            Bug ID: 47610
           Summary: No Man's Sky Crashes to Desktop after ~20 minutes
                    starting with wine-4.11 (Staging)
           Product: Wine
           Version: 4.13
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: critical
          Priority: P2
         Component: -unknown
          Assignee: wine-bugs at winehq.org
          Reporter: winebugz at kbrm.net
      Distribution: ---

Created attachment 65037
  --> https://bugs.winehq.org/attachment.cgi?id=65037
Winedbg failure dialog

Affected Wine: 4.11-4.13 Staging
WINEPREFIX:    Windows 7 (64-bit)
OpSys:         Debian GNU/Linux 9.9 (stretch)
Display:       NVIDIA Corporation GK104 [GeForce GTX 670] (rev a1)
Video Driver:  nvidia-driver 418.74-1~bpo9+1
DXVK:          1.3.2 OR uninstalled (does not seem to affect symptom)

No Man's Sky [Steam X.XX] [NMS BildID: 3397908] crashes to desktop randomly
anytime after 20-30 minutes of surface exploration or every time inter-planet
flight is attempted. Winedbg does not catch or record crash. Uncertain what the
trigger event is, but Traveling in Ship to any other in-system planet will
always trigger the crash.  But will also happen randomly in-game after the
20-minute mark.  

Absolutely reproducible for me by loading saved game - launching ship - fly
towards closest planet.  Game will crash just after launch, or mid-flight, or
even as the pulse engines shut off pre-landing - but always - cannot get to
surface of destination planet.

Issue does not occur in 4.10 Staging - with that version installed I can play
for multiple hours (2+ hrs on last run) without any issues.

Debug steps so far:
  Used Steam verify game files function - no issues found
  Deleted contents of Shader Cache and forced game to re-update (known crash
issue)
  Verified my CPU supports sse4_1 (known crash issue)
  Un-installed DXVK fron WINEPREFIX - no change in behavior in any version of
wine after 4.10 staging [4.10 + DXVK = OK]
  Downgraded wine (Staging) in steps from 4.13 down to 4.10 - running "wineboot
-u" each time before testing
  Problem goes away in 4.10 Staging - occurs in everything above that

Cannot seem to get winedbg to capture output - followed the instructions here:
https://wiki.winehq.org/Winedbg -
Got winedbg attached to the NME.exe wpid and game was running, when it crashed
"in flight" and all I got was:
"Process of pid=011c has terminated"
Wine-dbg>bt  
You must be attached to a process to run this command.

Not sure what else to include since wine is not trapping this crash?

Willing to try anything to test/resolve as downgrading to 4.10 breaks all of my
Blizzard games.

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