Closed Bug 1804030 Opened 3 years ago Closed 3 years ago

Startup crash in [@ _dl_close] caused by Mesa 22.3.0 when using Nvidia proprietary drivers: Fixed in Mesa 22.3.1

Categories

(Core :: Graphics, defect)

x86_64
Linux
defect

Tracking

()

RESOLVED MOVED

People

(Reporter: gsvelto, Assigned: ahale)

References

(Blocks 2 open bugs)

Details

(Keywords: crash)

Crash Data

Crash report: https://crash-stats.mozilla.org/report/index/3ff6129f-f662-48ef-b571-eeb7b0221205

Reason: SIGSEGV / SEGV_MAPERR

Top 10 frames of crashing thread:

0  ld-linux-x86-64.so.2  _dl_close  elf/elf/dl-close.c:795
1  libc.so.6  _dl_catch_exception  elf/elf/dl-error-skeleton.c:208
2  libc.so.6  _dl_catch_error  elf/elf/dl-error-skeleton.c:227
3  libc.so.6  _dlerror_run  dlfcn/dlfcn/dlerror.c:138
4  libc.so.6  dlclose@@GLIBC_2.34  dlfcn/dlfcn/dlclose.c:31
5  libgallium_dri.so  d3d12_destroy_screen  src/gallium/drivers/d3d12/d3d12_screen.cpp:744
6  libgallium_dri.so  d3d12_create_dxcore_screen  src/gallium/drivers/d3d12/d3d12_dxcore_screen.cpp:236
7  libgallium_dri.so  sw_screen_create_named  src/gallium/auxiliary/target-helpers/sw_helper.h:70
7  libgallium_dri.so  sw_screen_create_vk  src/gallium/auxiliary/target-helpers/sw_helper.h:102
8  libgallium_dri.so  pipe_loader_sw_create_screen  src/gallium/auxiliary/pipe-loader/pipe_loader_sw.c:425

Filing this in Graphics because maybe we want to block these versions. This is a startup crash which makes it particularly nasty. The bulk of the crashes are with version 510.85.2.0, 520.61.5.0, 520.56.6.0 and 515.48.7.0.

OS: Unspecified → Linux
Hardware: Unspecified → x86_64

The stack trace looks similar to mesa issue #7819 however that doesn't mention Nvidia drivers, and all the crash reports here are definitely using them. Maybe it's another manifestation of the same problem.

Given the timing with the release of Mesa 22.3 it could be that this is an incompatibility with Nvidia drivers that are not prepared to handle Mesa's new behavior.

The bug you link to clearly explains this is a bug in Mesa and the fix is in Mesa: it tries to free an invalid pointer when loading a secondary driver fails (which is where the NVIDIA link comes in).

Summary: Startup crash in [@ _dl_close] when using Nvidia proprietary drivers → Startup crash in [@ _dl_close] caused by Mesa 22.3.0 when using Nvidia proprietary drivers
Assignee: nobody → ahale
Severity: -- → S3
No longer blocks: gfx-triage

Status: I haven't gotten to testing this yet, it's assigned to me partly because one of the signatures is on WSL2 which I have experience with, so I'll try to debug that case and other repros I can attempt.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → MOVED
Summary: Startup crash in [@ _dl_close] caused by Mesa 22.3.0 when using Nvidia proprietary drivers → Startup crash in [@ _dl_close] caused by Mesa 22.3.0 when using Nvidia proprietary drivers: Fixed in Mesa 22.3.1
See Also: → 1844019
You need to log in before you can comment on or make changes to this bug.