Date: Sun, 13 Oct 2024 21:26:36 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 280846] Low memory freezes / OOM: a thread waited too long to allocate a page Message-ID: <bug-280846-227-P2LMCHFl0Q@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-280846-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280846 --- Comment #37 from Henrich Hartzer <henrichhartzer@tuta.io> --- Thank you! I'm running with the new patch to vm_pageout's vm_pageout_scan_inactive(). Will that have any impact on my system without swap? I've tested with ZFS with swap and without swap, as configured by the installer. All with geli, though. My setup with UFS has geli as well. Unfortunately, I was never tracking memory use to see if this accounting problem was present then. But, it's interesting that while running on UFS I had significant memory "locked" merely by having ZFS loaded, that was unaccounted for until I removed the module. Might it be part of the problem that I'm using geli, whether with UFS, ZFS, swap, or no swap? I haven't tried geli with UFS and swap, or just UFS, or just UFS+swap (no geli.) I don't have a way to add swap (other than file based) at the moment. I'd probably want to setup a separate system for testing with at that point. I wonder if Firefox has a genuine memory leak or if it's something more FreeBSD specific. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-280846-227-P2LMCHFl0Q>