3 ms·
Hah! Something new is also something old. Thanks for that. But won't you run into issues with child processes, of which Chrome tends to spawn a zillion? (I'
by yebyen 10y ago
Hah! Something new is also something old. Thanks for that.
But won't you run into issues with child processes, of which Chrome tends to spawn a zillion? (I'm reading that each one gets its own limit under ulimit...)
And potentially get your browser killed when it hits the limit? I haven't tested this and I don't really know how ulimit works, but I think it's a less effective solution than the cgroups for at least one reason.
- tyingq 10y agoYes, it is per process, so it would only limit memory-per-tab. I believe you get the "aw snap" window in chrome if it hits the limit.