Re: port-amd64/54988: possible memory leaks/swap problems

[mlh%goathill.org@localhost (MLH)]

The following reply was made to PR port-amd64/54988; it has been noted by GNATS.

From: mlh%goathill.org@localhost (MLH)
To: mlh%goathill.org@localhost
Cc: gnats-bugs%netbsd.org@localhost, ad%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, 
 netbsd-bugs%netbsd.org@localhost
Subject: Re: port-amd64/54988: possible memory leaks/swap problems
Date: Mon, 23 Mar 2020 10:06:12 -0400 (EDT)

 mlh wrote:
 > Andrew Doran wrote:
 > > The following reply was made to PR port-amd64/54988; it has been noted by GNATS.
 > > 
 > > From: Andrew Doran <ad%netbsd.org@localhost>
 > > To: gnats-bugs%netbsd.org@localhost
 > > Cc: 
 > > Subject: Re: port-amd64/54988: possible memory leaks/swap problems
 ... 
 > With the changes made yesterday as referenced by Andrew in:
 > Re: Another pmap panic:
 > 
 > > I suggest updaing to the latest, delivered yesterday, which has
 > > fixes for every problem I have encountered or seen mentioned
 > > including this one, and survives low memory stress testing for me:
 > 
 > I think this can be closed as it appears to have fixed these issues.
 
 I take that back. While the status is much better, there appears
 to still be a big memory leak as of yesterday.
 
 I booted NetBSD 9.99.51 : Sun Mar 22 22:42:31 and did a distribution
 build of -current. 4G of phymem, started the build with over 3.5G
 available, the build did finish without crashing but only about 6M
 of phymem is left available.
 
  r b      avm    fre  flt  re  pi   po   fr   sr w0 w1   in   sy  cs us sy id
  1 1   157916   6052 5540 103   5    6  362  600  6 127 660 10541 2276 3 2 96
 
 The box is barely usable running X and takes about 6 seconds to
 just switch focus to another window and about 15 seconds to launch
 another xterm. kmem-00192 still looks suspicious.
 
 Name        Size Requests Fail Releases Pgreq Pgrel Npage Hiwat Minpg Maxpg Idle
 kmem-00192   256 12942910    2     4093 808677    0 808677 808677   0   inf    0