Closed
Bug 1787714
Opened 2 years ago
Closed 2 years ago
VAAPI on dual Intel+Nvidia graphics: Crash in [@ statfs] in Nvidia proprietary drivers (libGLX_nvidia.so in RDD process)
Categories
(Core :: Security: Process Sandboxing, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1780312
Tracking | Status | |
---|---|---|
firefox106 | --- | disabled |
People
(Reporter: gsvelto, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: crash)
Crash Data
Crash report: https://crash-stats.mozilla.org/report/index/4397f601-c470-4b9b-9d24-20d8d0220828
Reason: SIGSYS / SYS_SECCOMP
Top 10 frames of crashing thread:
0 libc.so.6 statfs /usr/src/debug/glibc/sysdeps/unix/sysv/linux/statfs64.c:34
1 libnvidia-glcore.so.515.65.01 _nv011glcore
2 libnvidia-glcore.so.515.65.01 _nv011glcore
3 libnvidia-glcore.so.515.65.01 _nv011glcore
4 libGLX_nvidia.so.0 <.text ELF section in libGLX_nvidia.so.515.65.01>
5 libGLX_nvidia.so.0 vk_icdNegotiateLoaderICDInterfaceVersion
6 libGLX_nvidia.so.0 <.init ELF section in libGLX_nvidia.so.515.65.01>
7 ld-linux-x86-64.so.2 call_init /usr/src/debug/glibc/elf/dl-init.c:26
8 ld-linux-x86-64.so.2 _dl_init /usr/src/debug/glibc/elf/dl-init.c:117
9 libc.so.6 __GI__dl_catch_exception /usr/src/debug/glibc/elf/dl-error-skeleton.c:182
It looks like NVidia's proprietary drivers are at it again with some statfs calls.
Comment 1•2 years ago
|
||
"adapters": [
{
"description": "Mesa Intel(R) HD Graphics 630 (KBL GT2)",
"vendorID": "0x8086",
"deviceID": "0x5912",
"subsysID": null,
"RAM": 0,
"driver": null,
"driverVendor": "mesa/iris",
"driverVersion": "22.1.7.0",
"driverDate": null,
"GPUActive": true
},
{
"description": null,
"vendorID": "0x10de",
"deviceID": "0x1b06",
"subsysID": null,
"RAM": null,
"driver": null,
"driverVendor": null,
"driverVersion": null,
"driverDate": null,
"GPUActive": false
}
],
Blocks: 1748460
status-firefox106:
--- → disabled
Summary: Crash in [@ statfs] in Nvidia proprietary drivers → VAAPI on dual Intel+Nvidia graphics: Crash in [@ statfs] in Nvidia proprietary drivers (libGLX_nvidia.so in RDD process)
Updated•2 years ago
|
Comment 2•2 years ago
|
||
Looks like bug 1780312 with a slightly different crash signature; I'm going to assume that my attempt to avoid this statfs
didn't actually work.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•