Processing Ajax...

Title

Message

Confirm

Confirm

Confirm

Confirm

Are you sure you want to delete this item?

Confirm

Are you sure you want to delete this item?

Confirm

Are you sure?

User Image
David Atkinson1
5 discussion posts
Using DF 9.1 (non beta) with Win10 1709. I cycle my wallpaper from a local directory periodically. Following the historic memory issues with the previous releases I have been keeping an eye on memory usage. I have noticed perhaps anecdotally that following a change in wallpaper that the amount used by the "DisplayFusion" process will increase 1-2MB incrementally. This is not just the wallpaper size effect as over the period in question all papers have been cycle through at least once. Similarly the actual increase is relatively small 50% over 24 hours i.e 59 - 89 MB, however, if the machine is not restarted this could build up. Log file attached . (note that for the first 12h the PC was on but physically untouched overnight )
• Attachment [protected]: DisplayFusion.zip [395,482 bytes]
Nov 24, 2017  • #1
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Under 200 MB is fairly normal, depending on how many images you have in your selected wallpaper folders. Does it get higher than that?
Nov 27, 2017  • #2
User Image
David Atkinson1
5 discussion posts
Quote:
Under 200 MB is fairly normal, depending on how many images you have in your selected wallpaper folders. Does it get higher than that?


Not yet but is still slowly incrementing 1-2 MB each time the wallpaper changes, currently 145MB (will take another 24h minimum at current rate). Wallpapers are approx 35 files of 60MB total combined size from a single folder at resolutions suitable to span two monitors. Can see the spike as a wallpaper changes before it settles down again, always at a value slightly higher.
Nov 28, 2017  • #3
User Image
James S.
1 discussion post
I'm having a similar issue. I have a folder with 647 2560x1440 wallpapers and another with 134 1080x1920 wallpapers that change every minute. The memory usage by DF seems to increase at a fixed rate while the app is running regardless of weather the backgrounds are changing or not. I'm also having hard CPU spikes across all threads, I haven't been able to connect those spikes to anything specific other than they started after I installed DF. Not sure if this is connected to the memory usage problem. I've attached the debug zip DF generated.
• Attachment [protected]: DisplayFusionDebugInfo.zip [44,069 bytes]
Nov 29, 2017  • #4
Keith Lammers (BFS)'s profile on WallpaperFusion.com
@James: Thanks for attaching the troubleshooting info! Your issue is likely caused by Bitdefender. Please see this FAQ article for details: https://www.displayfusion.com/FAQ/#bitdefendermemoryleak

@David: If you add the "Handles," "GDI Objects," and "User Objects" columns to Task Manager, do any of those seem to increase consistently with wallpaper changes?
Dec 1, 2017  • #5
User Image
David Atkinson1
5 discussion posts
Quote:
@James: Thanks for attaching the troubleshooting info! Your issue is likely caused by Bitdefender. Please see this FAQ article for details: https://www.displayfusion.com/FAQ/#bitdefendermemoryleak

@David: If you add the "Handles," "GDI Objects," and "User Objects" columns to Task Manager, do any of those seem to increase consistently with wallpaper changes?


Added the columns and will advise.
Just started a second cycle yesterday, got to circa 200MB and reset back to 55MB before starting the slow increment again.(don't know if it was an unknown action on my part or part of the behaviour) . It's not particularly an issue for me particularly if it resets @200MB but is more academic interest and maybe some use to you.

Update (4/12/17) : No increment in any of the requested variables with wallpaper changes, all stable.
Dec 1, 2017 (modified Dec 4, 2017)  • #6
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Ok, thanks! That's fairly normal then. DisplayFusion will do some garbage collection after time that will clean up the memory usage which is why you're seeing it drop back down to 55 MB. If you like, you can enable a more aggressive memory trim with the "Troubleshooting > Memory Trim" option in the Settings > Advanced Settings window.
Dec 4, 2017  • #7
Subscribe to this discussion topic using RSS
Was this helpful?  Login to Vote(-)  Login to Vote(-)