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

    Memory leak with f.lux 4.100 and Windows 10 version 1903

    Windows v4
    4
    22
    3.7k
    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
      dkozinn @herf
      last edited by

      @herf I have not installed a color profile. I assume you're talking about a Windows color profile, not Custom Colors in f.lux?

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

        Okay we have posted 4.102, which has a "watchdog" process that restarts f.lux whenever RAM usage goes >128MB. I don't like doing this, but it is a lot better than letting this leak go unchecked.

        We did our best not to flash the screen when the restart happens, but you might see a tiny flash.

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

          I found another problem (looking for changes in the system so we can fix them quickly) that was causing most of the leaking.

          Fortunately it means that the leak will be a lot slower, but unfortunately, this means that we may have some new bugs.

          Please let me know if you see any unexpected behavior from 4.103 (posting now).

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

            @herf I've got the new version now and I'll let you know if I see anything unusual. Thanks!

            1 Reply Last reply Reply Quote 0
            • I
              izzyb027
              last edited by

              I can also confirm this behavior on Windows version 190318-1202, F.lux has been using as much as 1.7 Gb of memory in the background, which I've seen using Resource Monitor. It is a constant problem when running the app. For the time being, I'm going to try and downgrade back to v3 to avoid the conflict on my machine, it's very annoying and renders the app too much of a cost for me.

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

                We've mostly worked around this on all the "current" versions:

                • Windows build 18362 and later
                • f.lux version 4.103

                If you have (windows build) 18362 you will get an update to 4.103 automatically. Some people are on 18361 or older, and they are still having problems, but Windows should upgrade you in that case?

                1 Reply Last reply Reply Quote 0
                • I
                  izzyb027
                  last edited by

                  I'll check on the windows store, perhaps i'm missing an update on there

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

                    It is not live there yet, but is submitted.

                    Generally if you are running Insider windows, we recommend beta f.lux from our website. That's where we test things out.

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

                      v4.103 is live on the website and in the Windows Store.
                      We want 18362 to be as stable as possible, even though it's not officially released yet.

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

                        @herf I'm now on 4.103 but I haven't seen issues since the automatic restart process was implemented in the previous version. Is the leak fixed in 4.103 or is it still doing the periodic restarts?

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

                          Restarter is still there but the leak is now slowed down - there were two API calls leaking and we were able to reduce the use of one of them.

                          1 Reply Last reply Reply Quote 0
                          • F
                            fhoech
                            last edited by

                            Has the specific memory leak been reported to Microsoft? I created a feedback hub entry a while ago, in case someone may want to upvote it, go ahead: gdi32 Get/SetDeviceGammaRamp leaks Memory since Win10 1903 update (link opens Win10 feedback hub) https://aka.ms/AA65mre

                            Possibly related (although I'm not sure if f.lux is affected): WcsGetUsePerUserProfiles and WcsSetUsePerUserProfiles leak registry key handles internally since 1903 update (link opens Win10 feedback hub) https://aka.ms/AA5wk9z

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

                              @fhoech yes we reported both of them. I do need to check on the profile leak also - we went from checking for profile changes frequently to once per day (so really, if you change your profile you need to restart f.lux).

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