Closed Bug 1793839 Opened 2 years ago Closed 2 years ago

Avoid sanitizer crash reports in glxtest

Categories

(Core :: Graphics, defect)

defect

Tracking

()

RESOLVED FIXED
107 Branch
Tracking Status
firefox107 --- fixed

People

(Reporter: truber, Assigned: truber)

Details

Attachments

(1 file)

Running an AddressSanitizer build with NVidia graphics, I get the following report at startup:

Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: VA-API test failed: Something unexpected went wrong. (t=2.08967) [GFX1-]: glxtest: VA-API test failed: Something unexpected went wrong.
==397065==ERROR: AddressSanitizer: SEGV on unknown address 0x0000000000d8 (pc 0x7fbd507a2814 bp 0x61500002ce00 sp 0x7fff39886108 T0)
==397065==The signal is caused by a READ memory access.
==397065==Hint: address points to the zero page.
    #0 0x7fbd507a2814 in XDisplayString (/usr/lib/libX11.so.6+0x2b814) (BuildId: 21e886e968772b7964d646f54c1faecc56734de9)
    #1 0x7fbd4f553a1c in __vaDriverInit_1_13 (/usr/lib/dri/nvidia_drv_video.so+0xda1c) (BuildId: 8976d88c463676c8a7a27a4fa06ab51a4f428200)
    #2 0x7fbd1edfcc9b  (/usr/lib/libva.so.2+0x3c9b) (BuildId: 53551f71c1e329a02561e3a9d5f5cf1b58c6965d)
    #3 0x7fbd1ee01df0 in vaInitialize (/usr/lib/libva.so.2+0x8df0) (BuildId: 53551f71c1e329a02561e3a9d5f5cf1b58c6965d)
    #4 0x7fbd37d4be80 in childvaapitest /builds/worker/checkouts/gecko/toolkit/xre/glxtest.cpp:1034:21
    #5 0x7fbd37d4e1d0 in vaapitest() /builds/worker/checkouts/gecko/toolkit/xre/glxtest.cpp:1093:19
    #6 0x7fbd37d4c877 in childgltest /builds/worker/checkouts/gecko/toolkit/xre/glxtest.cpp:1186:3
    #7 0x7fbd37d4e4dd in fire_glxtest_process() /builds/worker/checkouts/gecko/toolkit/xre/glxtest.cpp:1222:14
    #8 0x7fbd37d2d484 in XREMain::XRE_mainInit(bool*) /builds/worker/checkouts/gecko/toolkit/xre/nsAppRunner.cpp:4012:3
    #9 0x7fbd37d3f2c4 in XREMain::XRE_main(int, char**, mozilla::BootstrapConfig const&) /builds/worker/checkouts/gecko/toolkit/xre/nsAppRunner.cpp:5890:16
    #10 0x7fbd37d401bb in XRE_main(int, char**, mozilla::BootstrapConfig const&) /builds/worker/checkouts/gecko/toolkit/xre/nsAppRunner.cpp:5972:21
    #11 0x561244312806 in do_main(int, char**, char**) /builds/worker/checkouts/gecko/browser/app/nsBrowserApp.cpp:226:22
    #12 0x561244311aa7 in main /builds/worker/checkouts/gecko/browser/app/nsBrowserApp.cpp:430:16
    #13 0x7fbd54c1c28f  (/usr/lib/libc.so.6+0x2328f) (BuildId: 26c81e7e05ebaf40bac3523b7d76be0cd71fad82)
    #14 0x7fbd54c1c349 in __libc_start_main (/usr/lib/libc.so.6+0x23349) (BuildId: 26c81e7e05ebaf40bac3523b7d76be0cd71fad82)
    #15 0x5612442519b9 in _start (/home/truber/builds/m-c-20221005162222-fuzzing-asan-opt/firefox+0x7a9b9) (BuildId: 01ce11ccd8d6f24896c508096a2ea9620e94161f)

AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV (/usr/lib/libX11.so.6+0x2b814) (BuildId: 21e886e968772b7964d646f54c1faecc56734de9) in XDisplayString
==397065==ABORTING

Normally this is background noise, but in a fuzzing harness, it will be detected as a crash. Since the whole point of glxtest is to avoid crashes when probing drivers, it makes sense to avoid sanitizer crash reporting in this case.

This applies to all AddressSanitizer and fuzzing builds, since fuzzing debug builds use the UBSan segv handler too.

Pushed by jdschwa@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/57a5d8dd7a8c
Avoid sanitizer crash reports in glxtest r=gfx-reviewers,aosmond
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 107 Branch
QA Whiteboard: [qa-107b-p2]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: