Comment # 43 on bug 1165351 from Luis Chamberlain

(In reply to Thomas Blume from comment #42)
> So, the systemd user instance started in user-1001.slice ignores the limits
> of the slice for memory as well as for TasksMax.
> I guess this is the root cause of the issue.

Is the theory here still that the real root cause is the tirpc allocations for
each possible file descriptor, and also, now we are observing the user instance
ignore user slice limits on memory which *should* in theory contain bogus /
buggy allocations such as the tirp issue?

If so then should we really open two bugs ? One for libtirpc and one for
systemd?

> Franck, since the systemd user instance is started below the user-1001.slice
> I would expect that it respects the memory limit of the slice.
> Any idea why it doesn't?

Any idea if we can work around this by forcing this to a low limit somehow?

And -- what explains why we didn't observe this all the time? I mean even
though tuctuc no longer exhibits good behaviour, I'm sure any new install of
Tumbleweed shouldn't be OOM'ing. So a new install should demo a case where this
is not being observed. So -- *why* is this only observed on some systems but
not all?