With dmabuf enabled, content process memory is inflating until killed by earlyoom.
I'll keep an eye on my browsing activity and memory monitor to see if it's caused by any website in particular.

Not sure if it's a leak (Asan doesn't complain about anything) but the difference in resident memory is startling.
Here is the diff for the Web Content processes between two memory reports, loading the same tabs and with a similar usage time and pattern:

-4,353,293 ── page-faults-soft [8]
-5,464.71 MB ── resident [8]
-5,194.45 MB ── resident-peak [8]
-5,821.63 MB ── resident-unique [8]
-0.95 MB ── script-preloader-memmapped-cache [8]
-7,902.25 MB ── vsize [8]

Which preference do you actually enable?
Thanks.

Closing as the reporter is inactive. Please reopen if this can still be reproduced.