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

[Joerg Sonnenberger <joerg%bec.de@localhost>]

On Wed, Feb 19, 2020 at 10:00:02PM +0000, MLH wrote:
> The following reply was made to PR port-amd64/54988; it has been noted by GNATS.
> 
> From: mlh%goathill.org@localhost (MLH)
> To: gnats-bugs%netbsd.org@localhost
> Cc: mlh%goathill.org@localhost
> Subject: Re: port-amd64/54988: possible memory leaks/swap problems
> Date: Wed, 19 Feb 2020 16:56:27 -0500 (EST)
> 
>  gnats-admin%netbsd.org@localhost wrote:
>  > Thank you very much for your problem report.
>  > It has the internal identification `port-amd64/54988'.
>  > The individual assigned to look at your
>  > report is: port-amd64-maintainer. 
>  > 
>  > >Category:       port-amd64
>  > >Responsible:    port-amd64-maintainer
>  > >Synopsis:       system freezes shortly after physical memory is exhausted.
>  > >Arrival-Date:   Wed Feb 19 18:30:00 +0000 2020
>  
>  I noticed that the main consumers appear to be:
>  
>  $ vmstat -m
>  Memory resource pool statistics
>  Name        Size Requests Fail Releases Pgreq Pgrel Npage Hiwat Minpg Maxpg Idle
>  ...
>  ataspl       160  1264935    0  1264935     3     0     3     3     0   inf    3
>  ...
>  execargs    262144 1775776   0  1775776     8     0     8     8     0    16    8
>  ...
>  wapblinopl    40  2723208    0  2721719    15     0    15    15     0   inf    0

If requests ~= releases, it is no memory leak.

Joerg