Right, so it is indeed the kernel OOM reaper that's killing processes, as it should. Chromium frontend is doing what it should, in displaying the "dead" message.
What's next is deciding whether the usage of memory itself is a bug.
The internal URL
chrome://memory-redirect/
will show what's doing what, similar to "ps", if that helps testing.
AFAIK, Chromium's memory usage is better than old Firefox, but not as good as (post MemShrink) Firefox.
Right, so it is indeed the kernel OOM reaper that's killing processes, as it should. Chromium frontend is doing what it should, in displaying the "dead" message.
What's next is deciding whether the usage of memory itself is a bug.
The internal URL
chrome: //memory- redirect/
will show what's doing what, similar to "ps", if that helps testing.
AFAIK, Chromium's memory usage is better than old Firefox, but not as good as (post MemShrink) Firefox.