locked
local session manager how many handles are normal RRS feed

  • Question

  • We are observing more than 17000 handles for lsm process (it seats under svchost) on our windows 10 1709 machines. It consumes quite a lot of memory then. This situation is visible when machine was not restarted for a few days. How many handles are let's say normal for local session manager?
    Friday, August 3, 2018 6:16 AM

Answers

  • Hello,

    This question seems unrelated with SCOM. Please post in an appropriete forum to reach the right audience.

    Thanks!

    Cheers


    Sam (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" wherever applicable. Thanks!) Blog:AnalyticOps Insights Twitter:Sameer Mhaisekar

    Friday, August 3, 2018 7:17 AM
  • Hi,

    It seems this is a pure OS issue. As Sam suggested, for better archiving, it is suggested to post in the OS forum to see if anyone can help.

    Meanwhile, based on my personal experience, local session manager high memory usage may be caused by incorrect driver, corrupt system files, etc. We may try to check if we upgrade any drivers recently or run dism command to see if it helps.

    process id 1000

    process id 1000

    Hope the above information helps.

    -----------------------------------------------

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, August 6, 2018 1:40 AM

All replies

  • Hello,

    This question seems unrelated with SCOM. Please post in an appropriete forum to reach the right audience.

    Thanks!

    Cheers


    Sam (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" wherever applicable. Thanks!) Blog:AnalyticOps Insights Twitter:Sameer Mhaisekar

    Friday, August 3, 2018 7:17 AM
  • Hi,

    It seems this is a pure OS issue. As Sam suggested, for better archiving, it is suggested to post in the OS forum to see if anyone can help.

    Meanwhile, based on my personal experience, local session manager high memory usage may be caused by incorrect driver, corrupt system files, etc. We may try to check if we upgrade any drivers recently or run dism command to see if it helps.

    process id 1000

    process id 1000

    Hope the above information helps.

    -----------------------------------------------

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, August 6, 2018 1:40 AM