[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: port-amd64/54988: possible memory leaks/swap problems
The following reply was made to PR port-amd64/54988; it has been noted by GNATS.
From: Andrew Doran <ad%netbsd.org@localhost>
To: MLH <mlh%goathill.org@localhost>
Cc: gnats-bugs%netbsd.org@localhost, port-amd64-maintainer%netbsd.org@localhost,
Subject: Re: port-amd64/54988: possible memory leaks/swap problems
Date: Wed, 4 Mar 2020 21:58:13 +0000
On Wed, Mar 04, 2020 at 04:30:04PM -0500, MLH wrote:
> MLH wrote:
> > The following reply was made to PR port-amd64/54988; it has been noted by GNATS.
> > Any idea on what is preventing the memory from being released and
> > why it just locks up?
> With the changes to -current as of NetBSD 9.99.48 Sun Mar 1 17:38:46
> EST 2020, the complete lockups I was seeing when the 4G of phymem
> was exhausted as well as the other issues seems to have been somewhat
> The largest improvements were last week when the big uvm changes
> were checked in but I haven't seen a lockup since the last couple
> of changes made on Sat or Sun. Those appear to have finally made
> this system stable enough to use again, though there still appear
> to be memory alloc/dealloc and swap issues because I have to reboot
> at least once a day when phymem is exhausted and the system becomes
> unusable due to severe swapping. This is when basically nothing is
> still running and disc cache is only taking up a tiny bit of phymem
> and only a tiny bit of swap appears to be in use.
Thanks for reporting. Not to put a downer on things, but the UVM jumbo
commit was largely a mechnical one to change lock types. Any corrective
effect is by chance. Still investigation to do here.
Main Index |
Thread Index |