While investigating another issue, I may have found something relevant.
It wasn't possible to switch to another tty (Ctrl + Alt + F2):
A start job is running for Login Service...
Turns out this may be another systemd issue, which has its own limits.
The following config file was created, which apparently fixed the issue:
# mkdir /etc/systemd/logind.conf.d/
# /etc/systemd/logind.conf.d/systemd-stupid-limits.conf
LimitNOFILE=500000
LimitNPROC=100000
UserTasksMax=100000
After a reboot, Chrome does not crash anymore and switching to another tty is working again.
Not sure if this is the right solution, but it does seem to work so far.
If someone has a better idea, please post an answer.
For future reference, this was logged in /var/log/daemon.log when the tty wasn't working:
systemd[1]: Starting Login Service...
systemd[1]: systemd-logind.service: Main process exited, code=exited, status=1/FAILURE
systemd[1]: Failed to start Login Service.
systemd[1]: systemd-logind.service: Unit entered failed state.
systemd[1]: systemd-logind.service: Failed with result 'exit-code'.
systemd[1]: systemd-logind.service: Service has no hold-off time, scheduling restart.
systemd[1]: Stopped Login Service.
Best Answer
Part One: Download Available Dependencies.
Part Two: Get .deb files of Chromium
download-onlyflag/var/cache/apt/archivesand the .deb files will be there.Part 3: Disable Updates in Update Manager or other Update Software
will disable the Updates. You will only be able to install them manually.(From new .deb packages from 18.04).