Swap not being used, RAM not being released, CPU use at 100%

[Cortimi]

Memory usage continues to climb to 100%, even as applications are shut down. Swap file is not being used. CPU usage climbs to %100 even as applications are shut down.

After reboot, system will operate normally for a number of hours, until a virtual machine (Virtual Box) is run. At this point memory and CPU usage will climb until %100. Exiting programs and closing the VM does not resolve the issue.

More information in this thread, started by me:

https://discourse.ubuntubudgie.org/t/high-ram-use-no-swap-use/940/9

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-33-generic 4.15.0-33.36
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: cortimi 1688 F.... pulseaudio
 /dev/snd/controlC1: cortimi 1688 F.... pulseaudio
 /dev/snd/controlC0: cortimi 1688 F.... pulseaudio
CurrentDesktop: Budgie:GNOME
Date: Wed Aug 29 17:39:45 2018
InstallationDate: Installed on 2018-08-23 (6 days ago)
InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725.1)
MachineType: MSI MS-7817
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=10f46365-0845-48bb-a427-fe155f6085c0 ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-33-generic N/A
 linux-backports-modules-4.15.0-33-generic N/A
 linux-firmware 1.173.1
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/30/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.9
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H81M-P33 (MS-7817)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd03/30/2015:svnMSI:pnMS-7817:pvr1.0:rvnMSI:rnH81M-P33(MS-7817):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7817
dmi.product.version: 1.0
dmi.sys.vendor: MSI

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[Coeur Noir (coeur-noir)]

« system will operate normally for a number of hours, until a virtual machine (Virtual Box) is run »
then maybe some settings to do in VirtualBox ?
Or a bug there ?

[Cortimi (cortimi12)]

No. Closing VirtualBox means that the memory usage should be released. If the memory is still tied up after the program has closed with no processes running, then the kernel is at fault as it is the one controlling memory.

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc2

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]