Description of problem: Bash consistently leaks 2 file descriptors opened to /usr/share/bash-completion/completions when applying command completions. The problem arises also when the directory is completely empty, so it's not related to scripts installed there. Version-Release number of selected component (if applicable): bash-4.2.42-1.fc18.x86_64 How reproducible: Always Steps to Reproduce: 1. Press tab twice at the prompt. No command is needed. 2. Watch ls -l /proc/$$/fd become longer 3. Wait for Too many open files error Expected results: No additional file descriptors are kept open after completing the command.
So it belongs to bash-completion package.
That seems to come from us trying to source the /usr/share/bash-completion/completions dir itself in some scenarios, and bash leaking a fd on each such try. See bug 903833 for the bash one, candidate workaround applied in bash-completion upstream: http://anonscm.debian.org/gitweb/?p=bash-completion/bash-completion.git;a=commitdiff;h=fea1c17
(In reply to comment #2) > http://anonscm.debian.org/gitweb/?p=bash-completion/bash-completion.git; > a=commitdiff;h=fea1c17 Eh, that, and: http://anonscm.debian.org/gitweb/?p=bash-completion/bash-completion.git;a=commitdiff;h=c4cc3eb
Bug 903833 fixes the root cause so there's no need to wait for the bash-completion workaround. *** This bug has been marked as a duplicate of bug 903833 ***