https://www.displayfusion.com/Discussions/RSS/?TopicID=019dde5d-de51-74c1-9f7c-1b3852cb73a8 DisplayFusion RSS: High CPU usage and apparent .NET runtime thread amplification in DisplayFusion.exe Sun, 03 May 2026 05:01:47 GMT en hourly 1 https://www.displayfusion.com/Discussions/RSS/?TopicID=019dde5d-de51-74c1-9f7c-1b3852cb73a8 https://www.displayfusion.com/Discussions/View/high-cpu-usage-and-apparent-net-runtime-thread-amplification-in-displayfusionexe/?ID=019dde5d-de51-74c1-9f7c-1b3852cb73a8#2 Fri, 01 May 2026 17:16:17 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/high-cpu-usage-and-apparent-net-runtime-thread-amplification-in-displayfusionexe/?ID=019dde5d-de51-74c1-9f7c-1b3852cb73a8#2 DisplayFusion If you disable DisplayFusion taskbars, what does the usage show for the main DisplayFusion.exe in Task Manager > Details? ]]> https://www.displayfusion.com/Discussions/View/high-cpu-usage-and-apparent-net-runtime-thread-amplification-in-displayfusionexe/?ID=019dde5d-de51-74c1-9f7c-1b3852cb73a8 Thu, 30 Apr 2026 12:29:47 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/high-cpu-usage-and-apparent-net-runtime-thread-amplification-in-displayfusionexe/?ID=019dde5d-de51-74c1-9f7c-1b3852cb73a8 DisplayFusion This issue has been occurring for quite some time and has gradually become worse.

Please see the attached log file and screenshot.

My DisplayFusion settings have not changed for several years. However, over approximately the past year, DisplayFusion has become increasingly unreliable and has started causing recurring issues.

I only use a small portion of DisplayFusion’s functionality, so it would be useful if DisplayFusion offered modular installation options instead of requiring the full product installation. In my case, most of the installed features are never used, but the full product still appears to contribute to reliability or overhead concerns.

Expected behavior:
DisplayFusion should remain stable with unchanged long-term settings.

Actual behavior:
DisplayFusion has become progressively unreliable despite no intentional configuration changes.

Environment
Application: DisplayFusion
Process: DisplayFusion.exe
Observed process ID: 48948 in the provided System Informer screenshots

----

TLR
Additional diagnostic finding
Temporarily disabling TitleBar Buttons reduced DisplayFusion CPU usage, but high enumeration activity continued afterward. This indicates that the TitleBar Buttons subsystem is likely contributing to the high CPU condition, but it does not appear to be the only source of repeated work.

The remaining activity suggests another enumeration path may still be active, possibly involving service IPC, module inspection, taskbar or tray icon enumeration, monitor enumeration, hook polling, or window-state refresh processing.

This should not be treated as resolved by disabling TitleBar Buttons. The broader issue is that DisplayFusion continues to perform excessive repeated enumeration under a long-standing configuration that previously operated acceptably.

----

Summary
DisplayFusion.exe is exhibiting high CPU utilization and heavy runtime thread activity. The issue has existed for some time and has progressively worsened. The current evidence shows DisplayFusion.exe consuming approximately 51% to 73% CPU in captured states, with overall CPU load near saturation.

Observed behavior
- DisplayFusion.exe appears as the dominant CPU consumer.
- CPU meter shows very high total CPU activity.
- System Informer thread view shows many active DisplayFusion.exe threads associated with coreclr.dll.
- Repeated thread start addresses include coreclr.dll+0xcccc40.
- Multiple entries also reference coreclr.dll!KickOffThread.
- System Informer statistics show elevated CPU, CPU relative, cycle delta, and context switch values.
- DisplayFusion settings have not intentionally changed for several years.

Expected behavior
DisplayFusion should remain stable as a background utility and should not produce sustained or excessive CPU load under an unchanged long-term configuration.

Actual behavior
DisplayFusion.exe generates high CPU load and appears to create or run many active .NET runtime threads, degrading system responsiveness.

Evidence
- Screenshot 1: DisplayFusion.exe at approximately 51.45% CPU.
- Screenshot 2: DisplayFusion.exe thread list with many active coreclr.dll+0xcccc40 entries.
- Screenshot 3: DisplayFusion.exe thread list with multiple coreclr.dll!KickOffThread entries.
- Screenshot 4 through 6: Loaded module views showing DisplayFusion, .NET runtime, Windows Forms, scripting, hooks, and related dependencies.
- Screenshot 7: Process statistics showing elevated CPU-related counters and memory footprint.
- Screenshot 8: DisplayFusion.exe at approximately 73.39% CPU while total CPU is near saturation.

Impact
The issue causes recurring system performance problems and reduces confidence in DisplayFusion as a stable long-running utility.

Probable fault surface
- DisplayFusion background worker loop
- .NET runtime thread scheduling
- Hook or monitor polling logic
- Scripting subsystem
- Window management or monitor event handling
- Repeated event processing
- Excessive timer, observer, or polling activity
- Interaction with WMI, monitoring tools, hooks, or multi-monitor state ]]>