Memory leak with f.lux 4.100 and Windows 10 version 1903
-
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
-
@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).
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login