Date: Fri, 30 Aug 2024 03:00:08 +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-BUY5ByCOrP@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 #7 from Henrich Hartzer <henrichhartzer@tuta.io> --- Wow, you're right. I thought the numbers looked odd, but wasn't sure if it = was some top behavior I didn't understand. Here's the figures after booting and starting sway. Much more reasonable! last pid: 1642; load averages: 0.20, 0.07, 0.02; battery: 99%=20=20=20= =20=20=20=20=20=20=20=20=20=20 up 0+00:01:43 02:55= :59 71 processes: 2 running, 67 sleeping, 2 waiting CPU: 0.5% user, 0.0% nice, 0.9% system, 0.1% interrupt, 98.5% idle Mem: 100M Active, 118M Inact, 571M Wired, 56K Buf, 15G Free ARC: 191M Total, 32M MFU, 155M MRU, 814K Header, 2628K Other 145M Compressed, 202M Uncompressed, 1.39:1 Ratio This is after starting my usual set of apps. I'm pretty sure it just takes Firefox to cause this, though. last pid: 2111; load averages: 0.35, 0.28, 0.12; battery: 99%=20=20=20= =20=20=20=20=20=20=20=20=20=20 up 0+00:04:39 02:58= :55 111 processes: 2 running, 107 sleeping, 2 waiting CPU: 0.4% user, 0.0% nice, 1.6% system, 0.0% interrupt, 98.0% idle Mem: 1756M Active, 1181M Inact, 27M Laundry, 1820M Wired, 56K Buf, 11G Free ARC: 1196M Total, 256M MFU, 918M MRU, 6016K Anon, 3689K Header, 8645K Other 1096M Compressed, 1300M Uncompressed, 1.19:1 Ratio Pretty big dent in memory use, but no where near what it was before the reb= oot. --=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-BUY5ByCOrP>