[Bug 47610] New: No Man' s Sky Crashes to Desktop after ~20 minutes starting with wine-4.11 ( Staging)
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@winehq.org Reporter: winebugz@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.
https://bugs.winehq.org/show_bug.cgi?id=47610
--- Comment #1 from Kevin Brott winebugz@kbrm.net --- Created attachment 65038 --> https://bugs.winehq.org/attachment.cgi?id=65038 Steam system info output
https://bugs.winehq.org/show_bug.cgi?id=47610
Kevin Brott winebugz@kbrm.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Debian Keywords| |regression
https://bugs.winehq.org/show_bug.cgi?id=47610
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick@piezo-forte.be
--- Comment #2 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- (In reply to Kevin Brott from comment #0)
Not sure what else to include since wine is not trapping this crash?
Hello,
Please, attach a normal (=without WINEDEBUG) terminal output. Instructions can be found there: https://wiki.winehq.org/FAQ#get_log
Regards.
https://bugs.winehq.org/show_bug.cgi?id=47610
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|critical |normal
--- Comment #3 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Bug triage notification.
Issue in a single application is severity 'normal'. Read more about severity levels description there: https://wiki.winehq.org/Bugs#severity
Regards.
https://bugs.winehq.org/show_bug.cgi?id=47610
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4@web.de
--- Comment #4 from Fabian Maurer dark.shadow4@web.de --- A regression test would be useful (see https://wiki.winehq.org/Regression_Testing). Although it's probably a bunch of work, especially since the bug takes so long to manifest.
https://bugs.winehq.org/show_bug.cgi?id=47610
--- Comment #5 from Kevin Brott winebugz@kbrm.net --- Created attachment 65043 --> https://bugs.winehq.org/attachment.cgi?id=65043 winedbg backtrace of crash
Uncertain if this is the same crash because the game didn't vanish - or if it didn't vanish because winedbg actually caught this one. But it's the same behaviour - so pretty sure.
https://bugs.winehq.org/show_bug.cgi?id=47610
--- Comment #6 from Kevin Brott winebugz@kbrm.net --- Created attachment 65044 --> https://bugs.winehq.org/attachment.cgi?id=65044 console output after running 'wine NMS.exe'
'script' command output from running NME.exe at the command line also includes a manual invocation on winedbg and using the bt all command post-crash.
https://bugs.winehq.org/show_bug.cgi?id=47610
--- Comment #7 from Kevin Brott winebugz@kbrm.net --- Finally got time to work on this tonight * Truncated my .xsession-errors file in hopes I'd catch something interesting (didn't - just a couple of pasystray errors). * Started 'script' output to file - to capture terminal output * set WINEPREFIX * changed directory to ${WINEPREFIX}/drive_c/Program Files (x86)/Steam/steamapps/common/No Man's Sky/Binaries * ran 'wine NMS.exe' it fired up steam and then ran the game * jumped into my ship and headed for nearest planet * ran out of fuel part-way - mined asteroid for more and continued on Pulse engines to target planet - game crashed (elapsed time maybe 10 minutes total) * this time wine caught the crash and the game didn't vanish to desktop * had to force-kill the wine game session so winedbg would let me save the crash/backtrace
Attaching gzip'd nms-backtrace.txt and nm-debug.txt
Mea Culpa. Sorry about the severity mis-set, I think maybe I didn't assimilate that part of the Bugs doc correctly - read it then posted bug - and forgot to double-check that section.
Willing to do a regression test - but that may take a couple of days to get done with my current work schedule.
https://bugs.winehq.org/show_bug.cgi?id=47610
--- Comment #8 from Kevin Brott winebugz@kbrm.net --- Well- crud - a huge content/code update dropped today in No Man's Sky. And my testing has to come to a crashing halt on this bug. See newly attached screenshot - even with mostly-current nvidia binary blob drivers - the game will not even start any more because of a Vulkan initialization failure.
https://bugs.winehq.org/show_bug.cgi?id=47610
--- Comment #9 from Kevin Brott winebugz@kbrm.net --- Created attachment 65050 --> https://bugs.winehq.org/attachment.cgi?id=65050 No Man's Sky "Beyond" Vulkan Init Failure message
Update to game that dropped today - invalidates this bug - time to start a new one.
https://bugs.winehq.org/show_bug.cgi?id=47610
--- Comment #10 from Kevin Brott winebugz@kbrm.net --- Forgot to mention - tried installing dxvk-1.3.2 into the steam wine prefix to see if it would solve the Vulkan Init issue - but it didn't change anything.
https://bugs.winehq.org/show_bug.cgi?id=47610
fls2019 secondary4bugs@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |secondary4bugs@gmail.com
--- Comment #11 from fls2019 secondary4bugs@gmail.com --- Since the Beyond update on Wednesday this is native Vulkan game so any D3D/DXVK workarounds won't work.
Currently there are issues with drivers mainly performance on nvidia (low vram being a symptom) but also crashing on AMD. There could also be issues with wine or wine's vulkan loader that may be causing these although the game crashes for me when attempting to capture a renderdoc so I can't really upload something for someone to debug.
https://bugs.winehq.org/show_bug.cgi?id=47610
Kevin Brott winebugz@kbrm.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED
--- Comment #12 from Kevin Brott winebugz@kbrm.net --- This issue is no longer valid. Game rendering engine has changed radically enough that a new ticket/issue needs to be opened to address Vulkan driver issues.
https://bugs.winehq.org/show_bug.cgi?id=47610
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com Resolution|INVALID |ABANDONED Status|RESOLVED |CLOSED
--- Comment #13 from Zebediah Figura z.figura12@gmail.com --- Nitpicking and closing.
https://bugs.winehq.org/show_bug.cgi?id=47610
Kevin Brott winebugz@kbrm.net changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.winehq.org/sho | |w_bug.cgi?id=47686
https://bugs.winehq.org/show_bug.cgi?id=47610
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also|https://bugs.winehq.org/sho | |w_bug.cgi?id=47686 |
-
wine-bugs＠winehq.org