Date: Thu, 25 Aug 2022 19:47:54 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 256507] Apparent kernel memory leak in 12-STABLE/13.1-Release Message-ID: <bug-256507-227-6EaPSmAi9H@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-256507-227@https.bugs.freebsd.org/bugzilla/> References: <bug-256507-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=3D256507 --- Comment #14 from dave@jetcafe.org --- So I only wrote the script for the purposes of addressing comment 11. My ma= in source of data is said sysctls exported at intervals to prometheus, which is where I get the graph you can look at in the attachments here.=20 That being said, if stopping and restarting services released the lost memo= ry due to lazy reporting, it should have shown up in prometheus eventually. It= has not for the past few hours.=20 Additionally, bug #234559 seems to be a reporting issue. If that were only = the case, I would not have opened this bug. :) If you read the original comment= , a machine with this bug left to itself for long enough will start swapping, t= hen thrashing, and finally panic when the swap space is exhausted. --=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-256507-227-6EaPSmAi9H>