EXCEPTION_ACCESS_VIOLATION w/ libgallium_wgl.dll when using Mesa 3D in Blender 3.0 about mesa-dist-win HOT 10 OPEN

Try 23.3.1. Also you should try blender 3.3, 3.6 and 4.0, in this order, to see if crash stops. Meesa3D usually doesn't support software versions that are no longer supported if there are newer versions still supported.

from mesa-dist-win.

Try 23.3.1. Also you should try blender 3.3, 3.6 and 4.0, in this order, to see if crash stops. Meesa3D usually doesn't support software versions that are no longer supported if there are newer versions still supported.

@pal1000 thanks i'll try that

from mesa-dist-win.

@pal1000 with 23.3.1, I got the following results:
3.3 - Same error
3.6 - Zink: unable to load vulkan-1.dll <- Missing, installing the dll gives this error:

MESA: error: ZINK: vkEnumerateInstanceExtensionProperties failed
MESA: error: ZINK: vkCreateInstance failed (VK_ERROR_INITIALIZATION_FAILED)

But it ends up with the same error:

Error   : EXCEPTION_ACCESS_VIOLATION
Address : 0x0000026C37C96CA0
Module  :
Thread  : 00002a68

4.0 - Same error as 3.6

from mesa-dist-win.

Does the crash occurs with MSVC release, MinGW or both?

from mesa-dist-win.

Does the crash occurs with MSVC release, MinGW or both?

I only used MinGW

from mesa-dist-win.

Try MSVC. While llvmpipe and lavapipe drivers are a bit slower, it's more reliable overall.

from mesa-dist-win.

I get this failure (only msvc builds), ex: demo app https://www.winteracter.com/demo.htm

I don't get it with GALLIUM_DRIVER=llvmpipe but I do get it with GALLIUM_DRIVER=d3d12 (maybe that's the default?) FWIW. Thanks. Should I report upstream?

Here's the java wrapper message to it:

#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffa481971ab, pid=9212, tid=7940
#
# JRE version: OpenJDK Runtime Environment (17.0.2+8) (build 17.0.2+8-86)
# Java VM: OpenJDK 64-Bit Server VM (17.0.2+8-86, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, windows-amd64)
# Problematic frame:
# C  [libgallium_wgl.dll+0x5a71ab]
#
# No core dump will be written. Minidumps are not enabled by default on client versions of Windows
#
# If you would like to submit a bug report, please visit:
#   https://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

---------------  S U M M A R Y ------------

Command Line: redacted

Host: Intel(R) Core(TM) i5-2540M CPU @ 2.60GHz, 4 cores, 5G,  Windows 10 , 64 bit Build 19041 (10.0.19041.3636)
Time: Mon Jan  1 23:55:03 2024 Mountain Standard Time elapsed time: 20.230541 seconds (0d 0h 0m 20s)

---------------  T H R E A D  ---------------

Current thread (0x000002159fd1c470):  JavaThread "Render thread" [_thread_in_native, id=7940, stack(0x000000bd31000000,0x000000bd31100000)]

Stack: [0x000000bd31000000,0x000000bd31100000],  sp=0x000000bd310fe7b0,  free space=1017k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C  [libgallium_wgl.dll+0x5a71ab]

Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j  org.lwjgl.system.JNI.invokePPPP(IIJJJJ)J+0
j  org.lwjgl.glfw.GLFW.nglfwCreateWindow(IIJJJ)J+14
j  org.lwjgl.glfw.GLFW.glfwCreateWindow(IILjava/lang/CharSequence;JJ)J+34
j  epf.<init>(Lepg;Lepd;Leos;Ljava/lang/String;Ljava/lang/String;)V+281
j  ftz.a(Leos;Ljava/lang/String;Ljava/lang/String;)Lepf;+15
j  evi.<init>(Lfip;)V+785
j  net.minecraft.client.main.Main.main([Ljava/lang/String;)V+1482
v  ~StubRoutines::call_stub

from mesa-dist-win.

I get this failure (only msvc builds), ex: demo app https://www.winteracter.com/demo.htm

I don't get it with GALLIUM_DRIVER=llvmpipe but I do get it with GALLIUM_DRIVER=d3d12 (maybe that's the default?) FWIW. Thanks. Should I report upstream?

Yes, d3d12 is default if it can run. It should fallback to llvmpipe otherwise. Reporting upstream requires a call stack annotated by debug symbols. You'll need the debug info package and a debugger that understands MSVC PDB format. MSVC itself with Desktop Development for C++ workload or WinDbg from Windows SDK debugging tools would do it. The latter is harder to use but smaller install.

Host: Intel(R) Core(TM) i5-2540M CPU @ 2.60GHz, 4 cores, 5G, Windows 10 , 64 bit Build 19041 (10.0.19041.3636)

Without dGPU or eGPU this system should fallback to llvmpipe automatically.

from mesa-dist-win.

A possible explanation (if lavapipe is involved) is that swrast was pretty broken on 23.3.2 - see https://gitlab.freedesktop.org/mesa/mesa/-/issues/10371. I'm not 100% sure but this sounds like it might have been your problem.

Appreciate that this repo uses github releases and keeps old versions around - version pinning meant that our windows CI kept working fine despite linux CI exploding.

from mesa-dist-win.

Try MSVC. While llvmpipe and lavapipe drivers are a bit slower, it's more reliable overall.

Hey! software rendering (i.e lavapipe and llvmpipe) is terrible in my machine compared to native rendering

from mesa-dist-win.