dxvk: mingw-w64-binutils 2.34 causes crashes in DXVK

If DXVK is compiled with mingw-w64-binutils 2.34, DXVK crashes in various different ways.

mingw-w64-binutils 2.33 does not have this problem. binutils master also does not have this problem. mingw-w64-binutils 2.34-1 is the current version in ArchLinux repos. I’m bisecting this now.

Filing an issue to keep track of the various occurrences of this in various games.

Software information

Bayonetta, various others

System information

  • GPU: RTX 2080
  • Driver: Nvidia 440.66.12-1
  • Wine version: proton-tkg-5.8
  • DXVK version: 1.6.1 or master 6643c75

Apitrace file(s)

N/A

Log files

Wine crashes on

wine: Unhandled page fault on write access to 00000000 at address 00314BAD (thread 00c4), starting debugger...

or various other symptoms such as https://github.com/doitsujin/dxvk/issues/1622

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 22 (8 by maintainers)

Most upvoted comments

I’ve bisected this to be broken by binutils commit ea933f17c3c6b9fa1daf8d03baa34f7bec855d6c: “Release bfd_alloc memory in bfd_check_format_matches” between 2.33 and 2.34 release branches

and fixed by binutils commit b03202e32c8235997b3485b0b4655926ad97a1cc: “bfd_get_size cache” between 2.34 and master.

https://sourceware.org/bugzilla/show_bug.cgi?id=25993#c16

Fix is applied to 2.34 branch, but the .tar.gz source downloads from https://ftp.gnu.org/gnu/binutils/ likely won’t be updated, so Arch and other distros that use those downloads won’t get the fix in 2.34. You’d have to use you use the binutils-2_34-branch git branch to get it.

But binutils 2.35 will have this fix and is planned to be released in a month’s time.

Unless you’re a toolchain dev you shouldn’t depend on any live or master branch of toolchain. Been there, done that: wasting time and many cpu cycles.

This is now in the latest master of binutils.