[Bug] Brave crashes the AMD Graphics Driver

[fluentmoheshwar]

Bug Description and Repro

1. Install xanmod kernel
2. Install brave-bin in archlinux.
3. Launch brave without any flags.
4. Display goes black and amd crash pops.

Kernel version

Linux 7.0.2-locietta-WSL2-xanmod1

WSL version

WSL version: 2.6.3.0 Kernel version: 6.6.87.2-1 WSLg version: 1.0.71 MSRDC version: 1.2.6353 Direct3D version: 1.611.1-81528511 DXCore version: 10.0.26100.1-240331-1435.ge-release Windows version: 10.0.26200.8328

Windows version

Microsoft Windows [Version 10.0.26200.8328]

Distro

Arch Linux

Additional context

Only happens when running brave with no flags. Running brave --ozone-platform=wayland seems to be fine.

dmesg: https://pastebin.com/MdJ6Lz2E

brave command output: https://pastebin.com/e1vxuztw

[Locietta]

Thanks for trying out the kernel and report!

I checked the dmesg and Brave output. This does not look like a guest kernel panic/oops. The suspicious sequence is that Brave enters the WSLg/Mesa D3D12 path, then logs:

D3D12: Removing Device.
GL_OUT_OF_MEMORY ... Unexpected driver error

After that, /dev/dxg ioctls start failing with -19 (ENODEV), which means the host-side D3D/GPU device has already been reset or removed. So the kernel messages look like a result of the AMD driver reset, not the initial cause.

Our dxgkrnl is extracted from Microsoft’s official WSL kernel tree, so it is identical to the official implementation. I don’t think this is caused by a custom dxgkrnl patch.

Since brave --ozone-platform=wayland avoids the issue, this is likely specific to Chromium’s default X11/Xwayland graphics path under WSLg on AMD.

Could you also test these and share which ones crash vs. work?

brave --disable-gpu
brave --disable-vulkan
brave --ozone-platform=x11 --use-angle=swiftshader

And if possible, please provide:

glxinfo -B
vulkaninfo --summary
pacman -Q brave-bin mesa vulkan-icd-loader vulkan-mesa-layers vulkan-dzn
cat /mnt/wslg/weston.log

For now, please continue using the Wayland flag as the workaround.

[fluentmoheshwar]

Thanks for trying out the kernel and report!

I checked the dmesg and Brave output. This does not look like a guest kernel panic/oops. The suspicious sequence is that Brave enters the WSLg/Mesa D3D12 path, then logs:

D3D12: Removing Device.
GL_OUT_OF_MEMORY ... Unexpected driver error

After that, /dev/dxg ioctls start failing with -19 (ENODEV), which means the host-side D3D/GPU device has already been reset or removed. So the kernel messages look like a result of the AMD driver reset, not the initial cause.

Our dxgkrnl is extracted from Microsoft’s official WSL kernel tree, so it is identical to the official implementation. I don’t think this is caused by a custom dxgkrnl patch.

Since brave --ozone-platform=wayland avoids the issue, this is likely specific to Chromium’s default X11/Xwayland graphics path under WSLg on AMD.

Could you also test these and share which ones crash vs. work?

brave --disable-gpu
brave --disable-vulkan
brave --ozone-platform=x11 --use-angle=swiftshader
And if possible, please provide:

glxinfo -B
vulkaninfo --summary
pacman -Q brave-bin mesa vulkan-icd-loader vulkan-mesa-layers vulkan-dzn
cat /mnt/wslg/weston.log
For now, please continue using the Wayland flag as the workaround.

brave --disable-gpu works fine.
brave --disable-vulkan works for a few minutes. then crashes the whole windows (I had to hard reset the PC)
brave --ozone-platform=x11 --use-angle=swiftshader works.

glxinfo -B: https://pastebin.com/XddwycMb
vulkaninfo --summary: https://pastebin.com/WYp9kxDU

pacman -Q brave-bin mesa vulkan-icd-loader vulkan-mesa-layers vulkan-dzn:

brave-bin 1:1.89.145-1
mesa 1:26.0.6-1
vulkan-icd-loader 1.4.341.0-1
vulkan-mesa-layers 1:26.0.6-1
vulkan-dzn 1:26.0.6-1

weston.log: https://pastebin.com/13qZ90CK

[Locietta]

Your logs show WSLg/Mesa is currently using the integrated GPU:

D3D12 (AMD Radeon(TM) Graphics)
deviceType = PHYSICAL_DEVICE_TYPE_INTEGRATED_GPU
Unified memory: yes

If you do have a dGPU, could you try forcing WSLg/Mesa to use it and then retest brave?

On Windows, check GPU names with:

Get-CimInstance Win32_VideoController | Select-Object Name,AdapterRAM

Then in WSL, use a substring of the dGPU name, for example:

export MESA_D3D12_DEFAULT_ADAPTER_NAME=NVIDIA
# or: export MESA_D3D12_DEFAULT_ADAPTER_NAME="Radeon RX"

glxinfo -B
vulkaninfo --summary
brave

Please confirm whether glxinfo -B / vulkaninfo --summary switch away from the AMD iGPU, and whether Brave still crashes.

Reference: https://github.com/microsoft/wslg/wiki/GPU-selection-in-WSLg

[fluentmoheshwar]

Your logs show WSLg/Mesa is currently using the integrated GPU:

D3D12 (AMD Radeon(TM) Graphics)
deviceType = PHYSICAL_DEVICE_TYPE_INTEGRATED_GPU
Unified memory: yes

If you do have a dGPU, could you try forcing WSLg/Mesa to use it and then retest brave?

On Windows, check GPU names with:

Get-CimInstance Win32_VideoController | Select-Object Name,AdapterRAM
Then in WSL, use a substring of the dGPU name, for example:

export MESA_D3D12_DEFAULT_ADAPTER_NAME=NVIDIA

or: export MESA_D3D12_DEFAULT_ADAPTER_NAME="Radeon RX"

glxinfo -B
vulkaninfo --summary
brave
Please confirm whether glxinfo -B / vulkaninfo --summary switch away from the AMD iGPU, and whether Brave still crashes.

Reference: Wiki: GPU selection in WSLg (microsoft/wslg)

I don't have a GPU.