[Bug 280846] Low memory freezes / OOM: a thread waited too long to allocate a page

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280846

--- Comment #50 from Henrich Hartzer <henrichhartzer@tuta.io> ---
Thank you! That is interesting.

So the memory can be reclaimed if pushed out to swap, but I wonder if swap
would fill up fairly quickly.

Running with all of the patches I had some more OOM behavior.

I had a fairly light Firefox (a dozen tabs, nothing very heavy), some other
processes, and ran Gimp. I couldn't get very far with Gimp.

pid 1614 (firefox), jid 0, uid 1003, was killed: a thread waited too long to
allocate a page
iwn0: RF switch: radio disabled
wlan0: link state changed to DOWN
pid 11298 (firefox), jid 0, uid 1002, was killed: a thread waited too long to
allocate a page
pid 1532 (firefox), jid 0, uid 1002, was killed: failed to reclaim memory
pid 68014 (gimp-2.10), jid 0, uid 0, was killed: failed to reclaim memory

When the system starts to lock up, I kill the RF switch which usually helps it
become more responsive. You can see the "a thread waited too long to allocate a
page" error again.

With my main Firefox process dead I tried Gimp again. I could barely use it
before it died again.

pid 69150 (gimp-2.10), jid 0, uid 0, was killed: failed to reclaim memory
pid 98331 (keepassxc), jid 0, uid 0, was killed: failed to reclaim memory
pid 1729 (telegram-desktop), jid 0, uid 1002, was killed: failed to reclaim
memory

Is "failed to reclaim memory" from not being able to swap out the dirty pages?
I'm surprised by how much memory Firefox and Gimp use.

-- 
You are receiving this mail because:
You are the assignee for the bug.