Your message dated Sat, 12 Dec 2015 22:51:47 -0500
with message-id
<CANTw=mo3o9vd6cdpx58h_lxx8j_ae95u4by2twews1-csmf...@mail.gmail.com>
and subject line Re: [Pkg-chromium-maint] Bug#754291: chromium: Recent Chromium
builds readily exhaust Debian default 1024 open file soft ulimit
has caused the Debian Bug report #754291,
regarding chromium: Recent Chromium builds readily exhaust Debian default 1024
open file soft ulimit
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
754291: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754291
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: chromium
Version: 35.0.1916.153-2
Severity: normal
Tags: upstream patch
upstream bug:
https://code.google.com/p/chromium/issues/detail?id=137875
It's reasonably easy for the chromium parent process to hit the maximum
open files limit which defaults to 1024 open files per process on Debian.
A temporary workaround is to add:
ulimit -n $( ulimit -nH )
to the chromium launcher script, in order to up to up the soft limit to the
hardlimit (perhaps there should be a cap e.g. 65536 if the hard limit is
higher than that?).
FWIW some other distros have both lower soft limits and higher hard limits.
Possibly another workaround would be to add a file which raises the 'nofile'
default limit /etc/security/limits.d/ for local users (e.g. in the floppy,
audio, or video groups maybe?). I don't know what a "reasonable" upper
limit would be, I just know that I exceed the current limit of 1024
on a daily basis, but probably I have more tabs open than most people
(around 40 at the moment, in two profiles).
As mentioned in the upstream bug report, a better fix would be to have
proper error reporting when file opens fail.
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.14-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages chromium depends on:
ii chromium-inspector 35.0.1916.153-2
ii gconf-service 3.2.6-2
ii libasound2 1.0.27.2-4
ii libc6 2.19-4
ii libcairo2 1.12.16-2
ii libcap2 1:2.22-1.2
ii libcups2 1.7.3-6
ii libdbus-1-3 1.8.6-1
ii libexpat1 2.1.0-6
ii libfontconfig1 2.11.0-5
ii libfreetype6 2.5.2-1
ii libgcc1 1:4.9.0-7
ii libgconf-2-4 3.2.6-2
ii libgcrypt11 1.5.3-4
ii libgdk-pixbuf2.0-0 2.30.7-1
ii libglib2.0-0 2.40.0-3
ii libgnome-keyring0 3.4.1-1
ii libgtk2.0-0 2.24.24-1
ii libharfbuzz0b 0.9.29-1
ii libjpeg8 8d-2
ii libnspr4 2:4.10.6-1
ii libnss3 2:3.16.1-1
ii libpango-1.0-0 1.36.3-1
ii libpangocairo-1.0-0 1.36.3-1
ii libspeechd2 0.8-6
ii libspeex1 1.2~rc1.1-1
ii libstdc++6 4.9.0-7
ii libudev1 204-14
ii libx11-6 2:1.6.2-2
ii libxcomposite1 1:0.4.4-1
ii libxcursor1 1:1.1.14-1
ii libxdamage1 1:1.1.4-1
ii libxext6 2:1.3.2-1
ii libxfixes3 1:5.0.1-1
ii libxi6 2:1.7.2-1
ii libxml2 2.9.1+dfsg1-3
ii libxrandr2 2:1.4.2-1
ii libxrender1 1:0.9.8-1
ii libxslt1.1 1.1.28-2
ii libxss1 1:1.2.2-1
ii libxtst6 2:1.2.2-1
ii xdg-utils 1.1.0~rc1+git20111210-7.1
chromium recommends no packages.
Versions of packages chromium suggests:
pn chromium-l10n <none>
pn mozplugger <none>
-- Configuration Files:
/etc/chromium/default changed [not included]
-- debconf-show failed
--- End Message ---
--- Begin Message ---
Limits are best set by the administrator and/or user (or a wrapper script).
Note that systemd chooses better default limits (in my opinion) than
sysvinit, so this is already solved for most users, those that did a
default install.
$ cat /proc/1/limits | grep open
Max open files 65536 65536 files
Best wishes,
Mike
--- End Message ---
