Processing Ajax...

Close Dialog


Close Dialog

Close Dialog

More of the Same . . . ?

User Image
66 discussion posts
I just installed beta 17, on a new Win 10 x64 Pro laptop:

1) You are installing 48 language files when just one is required.

2) When did you start using the #*@#$!!@&#@!! WebView2? If the answer isn't at least several years ago, does the bug/problem count correlate to that switch?

3) As a curiosity, what are all the xxx.dll.config files for? All but 2 seem to be identical.

4) I imported a DF backup from an earlier beta. When I try to apply the "4K_Top_Centered_Split_Laptop_Bottom" profile, I get the following error:

An error has occurred while applying your new Monitor configuration.
Please check your settings and try again.
Error: Failed to call SetDisplayConfig. [HR: ERROR_INVALID_PARAMETER]

I have attached the settings backup I imported.

5) With just DF running, with no profile applied, no triggers, simple stuff:
a) The DisplayFusion.exe PID is averaging over 4000 page faults per second.
b) With multiple apps open, and doing nothing but letting ProcessMonitor run, DF is running over 7% of all registry hits. As always they are just a bunch of spamming of the same items.
c) One thing that may be new, I cannot recall for certain, but around 35-40 percent of all reg reads result in a buffer overflow. This seems to trigger a second - successful, call to the same item (although that could be an artifact of ProcMon). Is this something you can avoid?
d) There are more than a few NOT FOUNDS too.
e) Capture Start: 9/11/2022 10:57:54.6935843 AM
Capture Stop: 9/11/2022 10:58:43.2866472 AM

Not quite 49 seconds, 53652 accesses captured, or a fair bit over 1000 per second. Eyeballing them, I would say that at least 95% of them are complete duplicates - all within less than 1 minute.

6) The DisplayFusion.exe process has maybe 20-25 threads on start address coreclr.dll+0x33400. One of them eats CPU constantly and by itself seems to chew through more CPU cycles than all others combined, a handful seem to run constantly but with much lower CPU cycles, and most are idle excepting the occassional quick flare-up. Here is the stack trace for the main thread, although the look mostly similar from what I saw:


7) I would think that the lion's share of the app is based on registering event watchers, likely with a smattering of event timers as well. In my quick review of some thread stacks I didn't see many *Event* threads. The couple I came across were on threads that were using no CPU, as expected.

On the hole, I think that the performance may be a bit better. I cannot be certain because I don't want to pull out the ProcMon traces I have sent in the past. Also, my new laptop has a FAR more powerful CPU than my last laptop did. I think the IO may be down a good bit? But there is clearly just way too much registry spamming going on.

I am going to do a reboot and see if I can successfully switch to the Profile I had saved. I hope I don't lose all of those!! Because I (used to) travel a good bit, I have a wide array of monitor configs created.

Oh, I attached the DF Troubleshooting text. Let me know if you need more info/debugging.
• Attachment [protected]: DisplayFusion_Troubleshooting_Text_202209111219.txt [300,170 bytes]
24 days ago  • #1
Owen Muhlethaler (BFS)'s profile on
Thanks for letting us know, we have these on our list to look into so we'll let you know if we need any more info.

23 days ago  • #2
Was this helpful?  Login to Vote(-)  Login to Vote(-)