Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#63625 - [boost] boost::process system and child seem to cause file descriptor leaks
Attached to Project:
Arch Linux
Opened by Jussi Hietanen (jussihi) - Monday, 02 September 2019, 08:31 GMT
Last edited by Antonio Rojas (arojas) - Tuesday, 08 October 2019, 16:49 GMT
Opened by Jussi Hietanen (jussihi) - Monday, 02 September 2019, 08:31 GMT
Last edited by Antonio Rojas (arojas) - Tuesday, 08 October 2019, 16:49 GMT
|
DetailsDescription:
Running commands with boost::process::child or boost::process::system seem to cause file descriptor leaks. Additional info: boost 1.69.0-2 kernel 5.2.4-arch1-1-ARCH gcc (GCC) 9.1.0 Steps to reproduce: Compile and run the following, monitor /proc/PID/fd: #include <boost/process.hpp> #include <thread> #include <cstdlib> int main(void) { while(true) { std::this_thread::sleep_for(std::chrono::seconds(1)); std::system("/usr/bin/iptables -F"); } return 0; } |
This task depends upon
I will attach the correct source file to this comment.
Could this bug be patched for Arch's release of boost, or do I need to hotfix the issue myself? If you are planning to package the next version (1.70, which is already out), could you tell me when you're planning on doing that? I'm kind of dependent of boost::process in my projects.
Thanks.