reassign 1081794 src:mesa tags 1081794 + upstream retitle 1081794 file descriptor leak mesa_shader_cache_db severity 1081794 important
Hallo, 14.09.24 23:45 Thorsten Glaser: > First guess: is $DISPLAY set and points to a usable X11 server? Yes, this is a pure X11 session, no wayland. > Second guess: […] > Third… […] Did all that, including strace'ing, was puzzled by a jump in FD numbers there. > Out of ideas, otherwise. Further investigation shows FDs 10-109 and 110-209 filled with: .cache/mesa_shader_cache_db/part0/mesa_cache.db .cache/mesa_shader_cache_db/part0/mesa_cache.idx through .cache/mesa_shader_cache_db/part49/mesa_cache.db .cache/mesa_shader_cache_db/part49/mesa_cache.idx When running in xterm (started from krunner) instead of konsole, there is only the first such run of cache files and mksh doesn't complain. These files should definitely be opened CLOEXEC. https://bbs.archlinux.org/viewtopic.php?id=298957 So while there might be a problem in mksh with many FDs, I'm reassigning to src:mesa. Because of https://bbs.archlinux.org/viewtopic.php?id=298957 I assume an upstream bug. Since this adds 100 FDs (at least in my case) per exec() of a mesa-using binary in the call chain I'm bumbping severity. Grüße Timo
signature.asc
Description: This is a digitally signed message part.
