Date: Wed, 02 Oct 2024 02:13:44 +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-DJ5MUJNiDq@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-280846-227@https.bugs.freebsd.org/bugzilla/> References: <bug-280846-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D280846 --- Comment #19 from Henrich Hartzer <henrichhartzer@tuta.io> --- Ah, good to know about not counting buf. Thank you! I started getting another lockup. Decided to track memory figures and kill = some apps to see if it would make any difference. Before killing Firefox: Mem: 68M Active, 133M Inact, 916K Laundry, 1336M Wired, 774M Buf, 1397M Free Total: 2,934 After killing Firefox: Mem: 26M Active, 90M Inact, 244K Laundry, 1234M Wired, 772M Buf, 4651M Free Total: 6,001 After killing everything notable: Mem: 22M Active, 113M Inact, 56K Laundry, 1190M Wired, 772M Buf, 6159M Free Total: 7,484 --- As far as swap goes, I've run with and without it and had these problems. I currently don't have any swap, so I imagine setting those sysctls would hav= e no effect? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-280846-227-DJ5MUJNiDq>