Showing results for 
Search instead for 
Did you mean: 
Level 7
Report Inappropriate Content
Message 1 of 7

Nonpaged pool memory leak with WSL on Windows 10

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 -

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

Sorry for not putting all in the information in the post again. If you need any more information feel free to ask.

6 Replies

Re: Nonpaged pool memory leak with WSL on Windows 10

Heads up, I just had this problem on a new laptop.
Compiled Linux 2 times in WSL, and voilla according to taskmanager all 16GB of RAM were exhausted, and Windows wasn't able to shut down anymore. Reboot still worked however.

Re: Nonpaged pool memory leak with WSL on Windows 10

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

Compile it
export ARCH=arm CROSS_COMPILE=/opt/gcc-linaro-7.2.1-2017.11-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf-
cd linux
make mrproper
make dove_defconfig
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.

Re: Nonpaged pool memory leak with WSL on Windows 10

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. 


dmcgeary McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 5 of 7

Re: Nonpaged pool memory leak with WSL on Windows 10


 There is a leak in pooltag MFE0 that can be very evident when compiling code. 
I am working to have the known issues KB82450 updated.

Re: Nonpaged pool memory leak with WSL on Windows 10

Is there a fix for this yet?

Re: Nonpaged pool memory leak with WSL on Windows 10

WSL is important for us.

Any proceeding with this issue ?


You Deserve an Award
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from McAfee experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by McAfee employees.
Join the Community
Join the Community