Using WSL on Windows on a system with ENS 10.5 installed I ran into a nonpage pool memory leak in the pool tagged with MFE0.
During a web search I encountered an earlier question whcih suggests that the pool with that tag belongs to McAfee - https://community.mcafee.com/t5/VirusScan-Enterprise-VSE/VirusScan-Enterprise-leaks-nonpaged-pool/m-...
All the information I collected can be found in a report I filed with the WSL people:
I am using Windows 10 Version 1709 (OS Build 16299.214) and ENS 10.5.3.3178.
Sorry for not putting all in the information in the post again. If you need any more information feel free to ask.
Some more details on how to reproduce:
Get any Windows 10 System that has Windows Subsystem for Linux installed
Install Ubuntu from the Store
Install dependencies for compiling Linux
sudo apt update
sudo apt install build-essential bison flex bc
Install Linaro arm toolchain (I have a feeling any toolchain, targeting any cpu architecture, will work)
sudo tar -C /opt -xf gcc-linaro-7.2.1-2017.11-x86_64_arm-linux-gnueabihf.tar.xz
Get Linux source code
git clone https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux.git
export ARCH=arm CROSS_COMPILE=/opt/gcc-linaro-7.2.1-2017.11-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf-
make -j4 dtbs zImage modules
Watch RAM usage in Task Manager. Once the build has finished, no visible process will be using a huge chunk of yuour memory, only released on the next reboot.
After uninstalling Mc-Afee, and then rerunning make mrproper, make dove_defconfig, make
The RAM usage no longer grows unreasonably, and the system stays usable.
I am having exactly the same issue.
You do not even need to install a toolchain and cross compile.
If you just compile using make the problem will happen.
Download the new ePolicy Orchestrator (ePO) Support Center Extension which simplifies ePO management and provides support resources directly in the console. Learn more about ePO Support Center