I have seen this particular issue before with the 4.x series on older hardware with 3G or less of RAM. It is intermittent depending on the size of the update. It is definitely a system RAM handling issue, but given that is does not cripple the system with OOM problems it's neither a glitch nor a bug. There are some things you can experiment with.
1) Check your BIOS for internal graphics settings. Look for a frame buffer location option. If there is one choose the above RAM setting.
2) Do both of these together. Increase your swappiness setting. Default is 60. Try 80. Decrease your vfs cache pressure setting. Default is 100. Try 50. Your system will slow slightly but RAM will hold up better to big processes.
3) Watch for fifo errors, or underruns or overruns at bootup. Some older low end Intel Celerons actually do not run Linux kernels of any series without those errors. They work, but they are not programmable on some older OEM MOBOs.
TC
1) Check your BIOS for internal graphics settings. Look for a frame buffer location option. If there is one choose the above RAM setting.
2) Do both of these together. Increase your swappiness setting. Default is 60. Try 80. Decrease your vfs cache pressure setting. Default is 100. Try 50. Your system will slow slightly but RAM will hold up better to big processes.
3) Watch for fifo errors, or underruns or overruns at bootup. Some older low end Intel Celerons actually do not run Linux kernels of any series without those errors. They work, but they are not programmable on some older OEM MOBOs.
TC
All opinions expressed and all advice given by Trinidad Cruz on this forum are his responsibility alone and do not necessarily reflect the views or methods of the developers of Linux Lite. He is a citizen of the United States where it is acceptable to occasionally be uninformed and inept as long as you pay your taxes.