upgrade to 5.1.24 on Solaris X86 has severe memory leak

[scotth]

After upgrading to 5.1.24 on Solaris X86 starting the VM quickly used all the physical memory and swap forcing me to reboot the physical host.

After removing 5.1.24 and installing 5.1.22 the problem was resolved

Name: system/kernel

Summary: Core Kernel

Description: Core operating system kernel, device drivers and other

modules.

Category: System/Core

State: Installed

Publisher: solaris

Version: 0.5.11

Build Release: 5.11

Branch: 0.175.3.22.0.3.0

Packaging Date: June 29, 2017 04:01:24 PM

Last Install Time: July 20, 2017 04:50:26 PM

Size: 35.93 MB FMRI: pkg://solaris/system/[email protected],5.11-0.175.3.22.0.3.0:20170629T160124Z

Jul 20 11:55:48 monkey mac: [ID 469746 kern.info] NOTICE: vboxvnic0 registered Jul 20 11:55:48 monkey vboxdrv: [ID 702911 kern.notice] vboxdrv: XXXXXXXXXXXXXXXX VBoxEhciR0.r0 Jul 20 11:57:34 monkey afpd[1394]: [ID 702911 daemon.error] dsi_getsess: Resource temporarily unavailable Jul 20 11:57:34 monkey afpd[1394]: [ID 702911 daemon.error] dsi_start: session error: Resource temporarily unavailable Jul 20 11:57:39 monkey afpd[2354]: [ID 702911 daemon.notice] Login by sheisey (AFP3.4) Jul 20 12:01:22 monkey tmpfs: [ID 518458 kern.warning] WARNING: /system/volatile: File system full, swap space limit exceeded Jul 20 12:01:23 monkey afpd[2354]: [ID 702911 daemon.error] Conversion failed (CH_UCS2 to UCS-2):Resource temporarily unavailable Jul 20 12:01:23 monkey afpd[2354]: [ID 702911 daemon.error] dir_new(did: 458089) {21dfd, 21dfd}: couldn't set UCS2 name Jul 20 12:02:25 monkey afpd[2354]: [ID 702911 daemon.error] of_alloc: malloc: Resource temporarily unavailable Jul 20 12:03:00 monkey last message repeated 1 time Jul 20 12:05:48 monkey mDNSResponder: [ID 702911 daemon.warning] ERROR: getOptRdata - unknown opt 4 Jul 20 12:06:26 monkey last message repeated 38 times Jul 20 12:06:35 monkey tmpfs: [ID 518458 kern.warning] WARNING: /system/volatile: File system full, swap space limit exceeded

[Socratis]

This is a known regression. See ​"VirtualBox 5.1.24 - eating all memory..." (for the Solaris report) and ​"5.1.24-117012 excessive memory use" for the more detailed discussion on Windows hosts.

There is a workaround. Try a test build ≥ 117099 and please report back with any success or failures.

[pentagonik]

@scotth Any chance of confirming the fix using the above mentioned test build yet? Thanks.

[Frank Mehnert]

Fix is part of VBox 5.1.26.