I just updated to the latest beta build of Windows 11. Since then, Display Fusion has been using between 12-25% of CPU consistently. Any one else experiencing that?
I saw this post in another thread and can confirm that disabling DF's multi monitor taskbar causes CPU to be used normally (less than 5%). Reactivation causes CPU to sustain at 20+%
Beta 13. I had CPU problems on Beta 12 but Beta 13 fixed that. But now that I am on Windows 11 Beta build 22581, the CPU problem has returned even worse. I have isolated it to having DF's taskbars enabled. With them off, the CPU is normal. But of course, I want (and like) DF's taskbars!
Quote:
Hi Fred,
Are you on the stable or beta version of DisplayFusion?
Build 22581 beta was a disaster on my Dell XPS8940SE and my Dell XPS15 2in1 laptop. I was able to recover back to previous build via Casper 11 recovery on my desktop Pc. However, my laptop would not recover....so I just finished rebuilding it totally on Windows 10x64 Pro. I definitely caution everyone to watch out concerning Build 22581.
ASUS home built Pc on Windows 10 x64 Pro with 3 Dell U2719D monitors. Dell XPS 8940SE on Windows 11x64 Pro with 2 Dell U2719D monitors.
I never realised my PC was on the insider builds. Although it explains the frequent upgrades. Anyway, mine got updated to build 22581 and I have had to disable display fusion taskbars as the CPU is stays around 10-25%. I am wary of rolling back.
I know beta builds of Windows are not supported but just adding to the thread to say you are not alone.
Strange, we've been running that build but haven't noticed any spikes. Could everyone here send me a copy of their troubleshooting info? Here are the steps:
Open the Settings > Troubleshooting tab
Click the "Export Info to File" button
Reply with the file attached
@doubledoom is DisplayFusion whitelisted in your Anti Virus?
Build 14 seems to be a definite improvement over the recent past. My statistics from 3 systems: ~2% on one, ~4% on second, 4% with prolonged jumps to ~11% on third.
The build 14 went over time to a persistent 15-35%, this on the system with initial 4% or so. I went back to DF 9.7 there, just to be able to work. This is an unending nightmare!
I found that just disabling the DF taskbar brings CPU back down to 4% or less. FOr me at least, that clearly seems to be the problem.
Quote:
The build 14 went over time to a persistent 15-35%, this on the system with initial 4% or so. I went back to DF 9.7 there, just to be able to work. This is an unending nightmare!
Thanks, Fred. I am aware that the specific issue is tied to the taskbar, but then the multimonitor taskbar is an essential part for me of the multimonitor experience.
Agreed. That's why I am hoping that Owen and his team can find a solution.
Quote:
Thanks, Fred. I am aware that the specific issue is tied to the taskbar, but then the multimonitor taskbar is an essential part for me of the multimonitor experience.
@Owen
Additional information: I downgraded to 9.9 (off beta) and CPOU is now 4% or less with DF taskbars on. Not sure what the cause is. Not even entirely sure what I am missing with 10.0, but I am glad to get the DF taskbars back with non-outrageous CPU.
The system where DF Beta 14 swallowed more CPU time than any other process used 8-core Intel i7-4710HQ. The same DF has worked OK on 8-core i7-8650U and
on 4-core i5-6500.
Also @PawelDanielewicz, are all 3 systems running the same Windows build number?
Thanks!
I shouldn't have presumably posted in Win 11 thread, but the earlier thread got long and grew cold - I also simply missed the Win 11 label. My 3 systems are Win 10 as there is some software on each maintained by my workplace and I am not to switch to Win 11 myself. That most problematic system runs Win 10 Pro 21H2 build 19044.1586. The two OK systems run Win 10 Enterprise 21H1 19043.1586 and 21H2 19044.1586
Thanks Fred, we've had a few customers note a spike between those two versions, so we're going to take a look into it and see if we can make any improvements. We'll let you know if we have anything further.
Owen,
Thanks. just to be clear - when i uodated to beta 13 the CPU spike continued. Should I stay on beta 11 until I gear from you?
Quote:
Thanks Fred, we've had a few customers note a spike between those two versions, so we're going to take a look into it and see if we can make any improvements. We'll let you know if we have anything further.
@PawelDanielewicz Does the CPU usage start climbing after doing something specific, or does it happen as soon as you enable multi-monitor taskbars?
Owen,
the taskbars on the particular system are always on. After I installed DF Build 14, the CPU usage was low and it went up in my absence. I.e., I cannot really pin it but there was also no particular intense monitor usage activity going on, just presumably some browser windows open. At this moment I am there back to 9.7 as I was unable to work otherwise.
How long did it take for the CPU usage to climb to something noticeable? Was it across an entire day?
I could not quite afford to go back to the version known to eventually overtake my Win 10 Pro system, but I went to the new build 15 and after 12h it continues to operate within 4-9% range. The latter is not great, there are occasional 20% spikes, but at least I do not need to uninstall the build right away. For the sake of this message, I also installed the Build 15 on one of the Win 10 Enterprise systems and, so far, the build operates there at 2%.
Okay interesting, could you send me a copy of the troubleshooting info from the system that runs fine, and another from the system that runs with spikes? Preferably if you can grab the info while the CPU usage is high, if possible.
Beta 15 has displayfusion hovering around 45-70% use for the last 10 minutes. it was at the more typical 15% ballpark earlier in the day. I have a lot of browser tabs open but as I closed them, it did not reduce the use.
I noticed that the displayfusion icon has vanished from the system tray and clicking on the hidden icons in the system tray on the secondary monitors does not open the box with the hidden system tray icons. The up arrow appears frozen as its gone a solid colour unlike the rest of the taskbar.
edit: I have a program called Filecenter running and when that closed, the CPU use on displayfusion dropped back to 15% from the 50-60% mark. When I reopened it, displayfusion went back to the 50-60% mark. Filecenter is a document management program.
@doubledoom If you open the DisplayFusion Settings > Compatibility tab, add in that application and disable application hooks, is the CPU usage still high after a restart?
@doubledoom If you open the DisplayFusion Settings > Compatibility tab, add in that application and disable application hooks, is the CPU usage still high after a restart?
Thanks!
Yes, that fixed the very high use and now it is back to 8-18% CPU use. Thank you. I was hoping that may have been a lead to the issue but it appears not.
Glad to hear there's some improvements! Higher CPU usage with the taskbars enabled is expected, as it has to poll to keep various features updated. We'll continue to look into any ways we can improve that going forward.