Forum Discussion

KevHal's avatar
KevHal
Iron Contributor
Feb 13, 2025

Committed Memory issue

Hi,

One of our customers wants to put as many users onto a session host as possible. fair play, i'd most likely want that too.  So they have it enough Ram so they could do that. 

We are hitting a bit of a snag on the Committed memory and not sure how to tackle it. The session host has 64GB memory, but does not seem to be using it all. Instead its filling up the committed memory. When this reaches 100% things start going wrong, FSLogix service crashes and DWM crashes.  

Has anyone else come across this scenario. We just use the default Azure setting for System Managed onto the temp drive for the page file:

 

 

Have we set something up wrong?

 

Thanks.

 

1 Reply

  • Kidd_Ip's avatar
    Kidd_Ip
    MVP
    Feb 14, 2025

    Considering on below:

     

    • Check FSLogix Configuration: Ensure that FSLogix is properly configured. Sometimes, misconfigurations can lead to memory issues. 
    • Update FSLogix: Make sure you're using the latest version of FSLogix. Updates often include fixes for issues like the one you're experiencing.
    • Review Anti-Virus Settings: Anti-virus products can sometimes interfere with FSLogix operations. Ensure that your anti-virus software is properly configured to exclude FSLogix files and folders.
    • Adjust Page File Settings: Since you're using the default Azure setting for System Managed page file on the temp drive, consider adjusting the page file size or location. Moving the page file to a different drive or increasing its size might help alleviate the committed memory issue.

Resources