protonscr

[macOS] Crash on any use of Vulkan

wineclosed
ValveSoftware/wine#11 · opened 2018-08-28 by flukejones · updated 2020-04-09 · 1 comments · github
1 matching comments, n / p to jump
Fflukejones 2018-08-28 github

It appears that this only happens within the Valve modified sources:

luke@stardust:~/src/Proton/dist$ PROTON_NO_ESYNC=1 PROTON_DUMP_DEBUG_COMMANDS=1 STEAM_COMPAT_DATA_PATH="/Users/luke/.wine" ./proton run /Users/luke/Downloads/vkquake-1.00.0_win64/vkQuake.exe -basedir /Users/luke/quake/
Command line: Z:\Users\luke\Downloads\vkquake-1.00.0_win64\vkQuake.exe -basedir /Users/luke/quake/
Found SDL version 2.0.8
Detected 8 CPUs.
Quake 1.09 (c) id Software
GLQuake 1.00 (c) id Software
FitzQuake 0.85 (c) John Fitzgibbons
FitzQuake SDL port (c) SleepwalkR, Baker
QuakeSpasm 0.93.0 (c) Ozkan Sezer, Eric Wasylishen & others
vkQuake 1.00.0 (c) Axel Gneiting & others
Host_Init
Playing registered version.
Console initialized.
UDP Initialized
WIPX_OpenSocket: Address family not supported by protocol family
WIPX_Init: Unable to open control socket, IPX disabled
Server using protocol 666 (FitzQuake)
Exe: 20:55:34 Jun 11 2018
256.0 megabyte heap

Vulkan Initialization
[mvk-info] MoltenVK version 1.0.19. Vulkan version 1.0.83.
[mvk-info] GPU device:
		model: AMD Radeon Pro 560
		type: Discrete
		vendorID: 0x1002
		deviceID: 0x67ef
		pipelineCacheUUID: 00000000-0000-0000-0000-271300002723
	supports the following Metal Feature Sets:
		macOS GPU Family 1 v3
		macOS GPU Family 1 v2
		macOS GPU Family 1 v1
[mvk-info] GPU device:
		model: Intel(R) HD Graphics 630
		type: Integrated
		vendorID: 0x8086
		deviceID: 0x591b
		pipelineCacheUUID: 00000000-0000-0000-0000-271300002723
	supports the following Metal Feature Sets:
		macOS GPU Family 1 v3
		macOS GPU Family 1 v2
		macOS GPU Family 1 v1
wine: Unhandled page fault on read access to 0xffffffffffffffff at address 0x4742f774 (thread 0009), starting debugger...
winedbg: Internal crash at 0x43525885

This the same issue reported here.

When replacing the wine source in the Proton project with a fresh winehq version (devel or staging) this problem goes away.

PROTON_NO_ESYNC=1 has no effect.

Fflukejones 2018-08-28 github

Debugging also seems to crash:

luke@stardust:~/src/Proton/dist$ /tmp/proton_luke/winedbg_run 
WineDbg starting on pid 002a
winedbg: Internal crash at 0x42b25885
luke@stardust:~/src/Proton/dist$ /tmp/proton_luke/gdb_run 
002a:002b: create process 'Z:\Users\luke\Downloads\vkquake-1.00.0_win64\vkQuake.exe'/0x10da0 @0x140084378 (0<0>)
winedbg: Internal crash at 0x43325885
luke@stardust:~/src/Proton/dist$

Launch options

Upstream links