Bug 1233595
| Summary: | Please raise RLIMIT_NOFILE and RLIMIT_NPROC to prevent Chrome/Chromium crashes | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Luke Hutchison <luke.hutch> |
| Component: | distribution | Assignee: | Tomas Mraz <tmraz> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 31 | CC: | dennis, gansalmon, giallu, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab, mikhail.v.gavrilov, pbrobinson, tj.rothwell, tmraz |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-11-24 18:53:21 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: | |||
|
Description
Luke Hutchison
2015-06-19 09:09:30 UTC
PAM currently does not set the number of open descriptors limit and I do not plan to add such configuration. I will also remove the 20-nproc.conf in Rawhide as this configuration currently makes more problems than it solves. Where does the default number of open descriptors limit come from? Is it compiled into the kernel or something? AFAIK yes. OK, switching component to kernel. Thanks. We aren't changing this in the kernel source code. It's runtime tunable and can be done on a per user basis or via system wide scripts. Reassigning to the distribution component for further discussion. If the kernel default values are not appropriate for the contemporary machines and applications, they should be changed. But of course that needs to be discussed and changed upstream. This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle. Changing version to '23'. (As we did not run this process for some time, it could affect also pre-Fedora 23 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23 I've dropped the 20-nproc.conf in pam-1.2.1-2.fc23. Also for the changing of the systemwide defaults if kernel is not going to change some place other than pam should be used. The limits.conf affect only the user sessions and not daemons and other services. So, AFAICT the removal of 20-nprocconf fixes the processes issue, but the open files one is still there. pam won't ship a file to change defaults, and kernel won't change defaults from upstream. So, how can we deliver this to users? Please note I am mostly concerned about workstation, I found this bug out if frustration for my crashing chrome, but others would just blame the distro and move on. How other distributions handle the problem with open files and chrome? I still think the current kernel default limit might be inappropriate for current applications and it should be then changed. There is no sense to have to always change it to something else in distributions. Not sure about other distros (I use only Fedora or RHEL/CentOS :) but several hits appears with a search. The proposed solution is always tuning ulimit... On the other hand, I found these relevant issues: https://code.google.com/p/chromium/issues/detail?id=539567 https://code.google.com/p/chromium/issues/detail?id=367037 https://code.google.com/p/chromium/issues/detail?id=539590 So at least they are aware of the issue It's worth pointing out the obvious, that ulimit can only raise the soft limit as high as the hard limit unless you're root (then you can set the hard limit). So if your system hardlimit is to low, ulimit won't help you at application launch time. Re. comment #11: yes, the first and third of those linked bugs were just barely created in the Chromium bug tracker to track the file and process limit respectively. The second bug is a dup of the first, and was already merged into it. You can see a bunch of other dups in the first bug. (I believe there would be even more dups, except that this is a maddeningly hard bug to pin down: as a tab junkie I have run into this on every Linux install I have ever used, but for years I thought it was just Chrome being buggy, and I'm sure many other people have come to the same incorrect conclusion.) This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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. May be related: https://bugs.chromium.org/p/chromium/issues/detail?id=664474#c2 This is still a daily problem for tab junkies on Fedora 24. I started using the extension "The Great Suspender" to try to limit how many tabs were active at a given time (it replaces webpage content with a lightweight placeholder page when a tab hasn't been viewed in a while), and even with this, if I have a lot of tabs open already and I open 20-30 more to research a topic, Chrome will lock up hard and then possibly crash. Curiously, if I put the following into /etc/security/limits.conf: * soft nofile 1000000 * hard nofile 1000000 * soft nproc 30000 * hard nproc 30000 ..then it sets the "ulimit -n" limit for root to 1000000, but not for a regular user (the regular user's limit is still 1024). Any idea why the regular user's limit is not affected by this? -- [For reference, the corresponding Chrome bug about reducing file descriptor usage is the following]: https://bugs.chromium.org/p/chromium/issues/detail?id=539567 This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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. Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. I don't believe this bug was ever resolved for file limits -- reopening. I also wanted to point out that Chrome 67 switches on site isolation, which creates a much larger number of processes (one per open site, including for all iframes). So it is possible the process limit is going to become a problem again. https://security.googleblog.com/2018/07/mitigating-spectre-with-site-isolation.html This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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. I am still observing crashes in Google Chrome: https://bugs.chromium.org/p/chromium/issues/detail?id=840326 This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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. This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'. This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31. 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. Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |