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

[Jonathan Nieder]

Nicholas Bamber wrote:
> On 31/05/11 19:43, Jonathan Nieder wrote:
>> Nicholas Bamber wrote:

>>> Trickier than you make it sound since once it has happened I cannot
>>> start "top". I tried starting top and then chromium but then chromium
>>> did a segmentation fault.
>>
>> Um, is that reproducible?  If so, could you file a new bug for it?
>> These can be merged if they turn out to have the same cause.
[...]
> 	Your comment about ulimit was actually pretty helpful. There were some
> pretty harsh limits in /etc/security/limits.conf which I have commented
> out. Now it appears to be working.

Thanks for tracking it down.

So, I tried to reproduce this, like so:

	$ 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.

Any hints for reproducing the segfault you hit?