UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36

Steps to reproduce the problem:
1. Find the limit on processes on your Linux machine: cat /proc/sys/kernel/pid_max
2. Start close to that many processes (31000 on a limit of 32768 is enough). Chrome can already be started when you do this.
3. Try opening a couple of tabs.

What is the expected behavior?
Chome fails with a message about being unable to create more processes and a suggestion that I stop some other processes.

What went wrong?
Instead, I got Aw Snap pages, regular notifications that "Plugins X, Y, and Z have crashed, click to restart them" (which would immediately fail again when I clicked the box), new tabs that would open and allow me to type in URLs but would never actually load anything, and a wide variety of other mysterious failures. There was no hint as to a root cause provided except in STDERR.

Crashed report ID: 

How much crashed? Whole browser

Is it a problem with a plugin? N/A 

Did this work before? No 

Chrome version: 61.0.3163.100  Channel: stable
OS Version: 
Flash Version: Shockwave Flash 27.0 r0

stderr would show messages like this:

[1:5:1013/111916.160773:ERROR:platform_thread_posix.cc(119)] pthread_create: Resource temporarily unavailable
[1:1:1013/111923.295377:ERROR:platform_thread_posix.cc(119)] pthread_create: Resource temporarily unavailable
[1:1:1013/112005.866322:ERROR:platform_thread_posix.cc(119)] pthread_create: Resource temporarily unavailable
[1:1:1013/112006.506634:ERROR:platform_thread_posix.cc(119)] pthread_create: Resource temporarily unavailable
wget-log: Transport endpoint is not connected; disabling logging.
wget-log: Transport endpoint is not connected; disabling logging.
wget-log: Transport endpoint is not connected; disabling logging.