Bug 1857113

Summary: screen suffers from a performance issue caused by RLIMIT64
Product: [Fedora] Fedora Reporter: customercare
Component: screenAssignee: Vaclav Dolezal <vdolezal>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 31CC: jridky, lnykryn, ofalk, phracek, vdolezal
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-03 20:24:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
strace of screen none

Description customercare 2020-07-15 07:17:15 UTC
Created attachment 1701156 [details]
strace of screen

Description of problem:

if screen is run, it takes a long time to start, because it closes 512*1024 filehandles it never opened.

It's caused by the RLIMIT_NOFILE, set by systemd.

rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024, rlim_max=RLIM64_INFINITY}) = 0
prlimit64(0, RLIMIT_NOFILE, NULL, {rlim_cur=1024, rlim_max=512*1024}) = 0
close(524287)                           = -1 EBADF (Ungültiger Dateideskriptor)
close(524286)                           = -1 EBADF (Ungültiger Dateideskriptor)
close(524285)                           = -1 EBADF (Ungültiger Dateideskriptor)
close(524284)                           = -1 EBADF (Ungültiger Dateideskriptor)
close(524283)                           = -1 EBADF (Ungültiger Dateideskriptor)
close(524282)                           = -1 EBADF (Ungültiger Dateideskriptor)
close(524281)                           = -1 EBADF (Ungültiger Dateideskriptor)
close(524280)                           = -1 EBADF (Ungültiger Dateideskriptor)
close(524279)                           = -1 EBADF (Ungültiger Dateideskriptor)
...

See the other bugreport for more details.

A fixed version is needed ASAP and a detailed analyses how this bug got implemented would be helpfull, as other apps are affected by this too.

A discussion on FEDDEV ML is required in my eyes to check any other app for this bug. 


Version-Release number of selected component (if applicable):

screen-4.6.2-9

How reproducible:

100% 

Steps to Reproduce:

as root: 

strace -e close screen 

Actual results:

512*1024 close() on non existing filedescriptors

Expected results:

0 close() on non existing filedescriptors

Additional info:

Comment 1 Oliver Falk 2020-08-28 08:02:58 UTC
I can confirm this behaviour on F31 with screen 4.6. However, with screen 4.8 (already in Rawhide), this doesn't happen any longer.

Comment 2 Ben Cotton 2020-11-03 16:49:47 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 customercare 2020-11-03 20:24:04 UTC

*** This bug has been marked as a duplicate of bug 1852460 ***