Sudden grow of memory in "Laundry" state
Rozhuk Ivan
rozhuk.im at gmail.com
Mon Nov 5 22:21:13 UTC 2018
On Sat, 27 Oct 2018 07:38:19 +0300
Konstantin Belousov <kostikbel at gmail.com> wrote:
> > 1. When process allocates memory (mmap), "Active" memory increases,
> > "Free" memory decreases (that's expected).
> No, mmap(2) call only causes some small amount of the kernel memory
> allocation, to track the mmaped region.
>
> Pages are allocated on the first touch, lets ignore the prefaulting
> mechanism which is not too relevant for the discussion. Mapped page
> can be either active or inactive, this is determined by the usage
> history.
>
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195882
This is still a proublem.
I have 12.0b3 in vbox.
16 Gb hdd, 4 Gb RAM.
Free 6+Gb on hdd.
Build app to write 6 Gb.
run, it was killed
Nov 5 21:05:09 firewall kernel: pid 96603 (testvm), uid 0, was killed: out of swap space
Nov 5 21:05:15 firewall kernel: Nov 5 21:05:09 firewall kernel: pid 96603 (testvm), uid 0, was killed: out of swap space
Mem: 50M Active, 3331M Inact, 192M Laundry, 362M Wired, 208M Buf, 212M Free
Swap: 16G Total, 151M Used, 16G Free
Filesystem Size Used Avail Capacity iused ifree %iused Mounted on
/dev/gptid/6f42a7d9-45b9-11e8-8fd8-0800278fa2e3 17G 14G 2.4G 85% 768k 1.4M 35% /
1. Program does not do it job / killed, but system have more than enough swap.
2. mem does not free after all disk io done.
It free only after file deleted or readed.
Also there is more strange behaviour if swap file disabled.
More information about the freebsd-hackers
mailing list