Chrome too many files open / crash / Sorry Jim

It is Important to know that there are two kinds of limits:

• A hard limit is configurable by root only. This is the highest possible value (limit) for the soft limit.
• A soft limit can be set by an ordinary user. This is the actual limit in effect.

Solution for a single session

In the shell set the soft limit:

ulimit -Sn 2048

This example will raise the actual limit to 2048 but the command will succeed only if the hard limit (check: ulimit -Hn) is the same or higher. If you need higher values, raise the hard limit using one of the methods below. The limits are set per process and they are inherited by newly spawned processes, so anything you run after this command in the same shell will have the new limits.

Changing hard limit in a single session

This is not easy because only root can change a hard limit and after switching to root you have to switch back to the original user. Here is the solution with sudo:

sudo sh -c "ulimit -Hn 9000 ; exec su \"$USER\""

System-wide solution

In Debian and many other systems using pam_limits you can set the system-wide limits in /etc/security/limits.conf and in files in /etc/security/limits.d. The conf file contains description. Example lines:

@webadmins       hard     nofile     16384
@webadmins       soft     nofile      8192

This will set the hard limit and default soft limit for users in group webadmins after login.

Other limits

The hard limit value is limited by global limit of open file descriptors value in /proc/sys/fs/file-max which is pretty high by default in modern Linux distributions. This value is limited by NR_OPEN value used during kernel compilation.

Is there not a better solution?

Maybe you could check if all the *log files you feed to tail -f are really active files which need to be monitored. It is possible that some of them are already closed for logging and you can just open a smaller number of files.

You are presumably using the i915 driver for the integrated video, and I bet it has something to do with this bug:

https://bugzilla.kernel.org/show_bug.cgi?id=58381

Since the "freezing" is a kernel panic. Try:

grep i915_hangcheck_hung /var/log/*

And see what turns up. You might try turning off "use hardware acceleration when available" in chrome (under "Advanced Settings...System").

There's also a suggestion here (the above bug seems to be considered a duplicate of this one, but the one above has a better initial report involving chrome) to try this:

echo 0 | sudo dd of=/sys/module/i915/parameters/semaphores

If you do that su root it is a bit simpler:

echo 0 > /sys/module/i915/parameters/semaphores

Beware that the files in /sys are not real files on disk -- sysfs is a kernel interface. Reading a file is a request for live information from the kernel, and writing to a file is a live request to set a parameter. So this is not a permanent configuration that will persist across re-boots. You could include the echo command in a boot script, or add a kernel command line parameter in your grub.conf, as per the second bug report link:

i915.semaphores=0

Which will set that parameter at boot.