Bug#628724: chromium: Browser prevents urther creation of processes

[Jonathan Nieder]

Jonathan Nieder wrote:

>	$ ulimit -u 60
>	$ chromium
>	[2052:2052:480034618537:FATAL:zygote_host_linux.cc(175)] Check failed: pid_ > 0. Did not find zygote process (using sandbox binary /usr/lib/chromium/chromium-sandbox)
>	Aborted (core dumped)
>
> That's not ideal (it would be better to have a message about not being
> able to fork because a resource is temporarily unavailable :)), but it's
> not a segfault.

Related bug:

	$ ulimit -u 80
	$ chromium
	[... open a few tabs ...]
	[1:1:480224295285:ERROR:zygote_main_linux.cc(410)] Zygote could not fork: 11
	[1:1:480224295334:ERROR:zygote_main_linux.cc(423)] Error parsing fork request from browser

and any new tabs or requests just hang from then on.  Closing the
browser leaves it hanging.

	^CHandling SIGINT.
	Successfully wrote to shutdown pipe, resetting signal handler.
	Handling SIGINT.
	Check failed: g_shutdown_pipe_write_fd != -1
	^C
	$

Still not the hoped-for segfault yet.