f.lux f.lux forum
    • Recent
    • Popular
    • Register
    • Login

    F.lux handle bug

    Windows v4
    2
    8
    1.2k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • D
      destroyer
      last edited by

      F.lux is using thousands of handles when i leave my pc on for more than a day.
      I was looking into process explorer and found out it's this key
      HKLM\SYSTEM\ControlSet001\Control\Class{4d36e96e-e325-11ce-bfc1-08002be10318}

      I was using windows store version but that apparently isn't updated anymore (?), so I've installed latest v4.99 but the issue persists. Win10 x64 v1809

      1 Reply Last reply Reply Quote 0
      • herfH
        herf
        last edited by

        This post is deleted!
        1 Reply Last reply Reply Quote 0
        • herfH
          herf
          last edited by

          Ugh I thought we fixed this but there is a leak in one of the Windows API calls we're making.

          Will see what can be done.

          herfH 1 Reply Last reply Reply Quote 0
          • herfH
            herf @herf
            last edited by

            4.100 has a workaround, mainly that we stop looking for color profile changes every two minutes. So if you change your profile you now have to restart f.lux.

            Also @destroyer do you have one monitor or more than one?

            Please try the beta and let us know:

            https://forum.justgetflux.com/topic/6289/to-join-the-f-lux-beta

            1 Reply Last reply Reply Quote 0
            • D
              destroyer
              last edited by

              Thanks for reply --
              Joined beta, 4.100 installed ... will report results in couple days.
              And yes, I do use two monitors, one is connected to nvidia gtx 760 and the other one to intel hd 530

              1 Reply Last reply Reply Quote 0
              • herfH
                herf
                last edited by

                Update:

                1. You need dual displays to see this bug, and
                2. It does not happen on Windows 7.
                3. We've reduced the number of calls substantially in 4.100, so it shouldn't be a problem for most cases.
                1 Reply Last reply Reply Quote 0
                • D
                  destroyer
                  last edited by

                  Since my last response I see 705 handles in total. Most of them is still to that key but the number is significantly lower (about 20x) than before and it doesn't seem to be growing so I think the mitigation was successful :)

                  Btw any plans to provide updates to the win store version of the app or should I just install the exe from website on my other PCs?

                  1 Reply Last reply Reply Quote 0
                  • herfH
                    herf
                    last edited by

                    Our 4.101 beta is doing even more aggressive caching of the leaky call, should show slightly lower numbers.

                    1 Reply Last reply Reply Quote 0
                    • First post
                      Last post
                    Copyright © 2014 NodeBB Forums | Contributors