Forum Discussion

mcorcoran's avatar
mcorcoran
New Contributor
6 years ago

handle usage continues to grow

So I've noticed that handle usage continues to grow with system uptime it seems. I'm not sure exactly, since this is above my paygrade, how detrimental token handles are, but any time resources are allocated and never freed is usually not a good thing. I'm afraid that once the handle count reaches a certain point with certain systems that system resources become exhausted and simple tasks such as opening Windows Explorer or a command prompt is unsuccessful. It seems that there's something missing in the token handle creation process that's stuck in a loop and continually creates new token handles while never closing/erasing/deleting the ones that were already created. Is this something that could be looked into from the development side? It just comes across as abnormal application behavior. Thanks.

 

Edit:  The pics below were taken from different systems with different uptimes, thus their handle counts vary, but it's the same problem where it'll continue to grow the longer the system isn't rebooted/Logmein service or executable isn't restarted.



This message has 0 replies

 

    • mcorcoran's avatar
      mcorcoran
      New Contributor
      6 years ago
      milles wrote:

      What version are you running?

       

       

      On the test box, just plain Win10 I have running, the Logmein version is 4.1.12382 and Logmein Client version is 1.3.4446, but haven't noticed anything strange with the LMI client or the RC executables, just specifically the Logmein.exe process that seems to have the handle leak. Even on multiple systems I've checkd, Win7/Win10 and 32/64-bit, they will randomly show the same behavior, but not all of them. So not exactly sure what's causing this.

      • AshC's avatar
        AshC
        Retired GoTo Contributor
        6 years ago

        mcorcoran  I don't have any examples of LMI Central causing this behavior on the newest builds.  If you are running version 12382 or higher then this should not be occurring at all.

         

        In this case, you should create a case directly with our Customer Support team for assistance in documenting the affected environment, and gathering log files for in-depth review.