Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 12 May 2023 01:39:29 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 271246] Kernel wired memory leak with repeated netstat
Message-ID:  <bug-271246-227-rqi8CbEME3@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-271246-227@https.bugs.freebsd.org/bugzilla/>
References:  <bug-271246-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=3D271246

--- Comment #25 from Dave Hayes <dave@jetcafe.org> ---
So, as part of monitoring, the machine in question does repeated netstats a=
nd
hence is always in that state. It's just a matter of figuring out what
statistics are useful to you in finding the problem, as I likely collect way
too much. As you might have noticed, I can produce graphs of any sysctl MIB
that is exposed to root users.=20

Here is the information you requested:

  Mem: 66M Active, 1015M Inact, 4439M Wired, 1419M Buf, 10G Free

It took some weeks for the machine to start thrashing last time, this is
because the leak is very slow. My while loop above is just to make the leak
more apparent. That vm pgcache value is still growing, even though I turned=
 the
loop off (as is wired memory).

--=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-271246-227-rqi8CbEME3>