On Tue 07-01-20 21:44:12, Pavel Machek wrote: > Hi! > > I updated my userspace to x86-64, and now chromium likes to eat all > the memory and bring the system to standstill. > > Unfortunately, OOM killer does not react: > > I'm now running "ps aux", and it prints one line every 20 seconds or > more. Do we agree that is "unusable" system? I attempted to do kill > from other session. Does sysrq+f help? > Do we agree that OOM killer should have reacted way sooner? This is impossible to answer without knowing what was going on at the time. Was the system threshing over page cache/swap? In other words, is the system completely out of memory or refaulting the working set all the time because it doesn't fit into memory? > Is there something I can tweak to make it behave more reasonably? PSI based early OOM killing might help. See https://github.com/facebookincubator/oomd -- Michal Hocko SUSE Labs
