Hi,

I’ve recently changed one of my monitors and updated the graphic card drivers and since then display fusion seems to be unable to switch to a specific monitor profile. If recreated the affected monitor profile (‘tv’) in version 9.7.12 and 9.8b12. In both version the effect is the same.

Once I try to switch to the ‘tv’ profile the current monitor setup is not modified. It seems that DisplayFusion is hanging or blocked (running at around 12-14% CPU load which would be one virtual core). Only the only way to access display fusion again is to kill the not responding process.

Previously everything word fine. The only thing that changes was the following:
- Switched one of the monitors
- Since I also need to use the 24’’ monitor for other laptops and lack of usable input/output interfaces, the monitor is not directly connected via dvi but dvi -> hdmi switch -> dvi. However, this does not seem to have an effect regarding display fusion.
- Updated to the latest driver of the graphic card
I’ve attached to log output for versions 9.7.12 as well as 9.8 beta 12.

Previously the profile used to work. However, that was some time ago and I did not use the profile for some weeks. Since then, I changed the monitor setup and had some issues with the previous graphic card driver (VLC crashed sometimes if hw-acceleration was enabled), I upgraded the driver as well and created a new profile replacing the old one.

Recreating the 'tv' profile using the usual windows tools is working for the display part without problems. There is only one additional issue that cloning the desktop does seem have an effect that the hdmi audio output device is lost, but that seems to be a windows/driver issue and I will check that sometime later.

Reapplying the stored 'tv' setup with DisplayFusion has the described effect of a frozen DisplayFusion and no monitor setup changes.

One short update. I’ve recently switched to the current release version 9.8 of DisplayFusion and did a clean reinstall of the AMD graphic drivers. This solved the HDMI issues, but the DisplayFusion issue is still present.

Switching from the ‘default’ to the ‘tv’ profile is not possible and DisplayFusion is probably hanging in an endless loop. However, I accidentally discovered one workaround for the issue. I’ve another profile ‘work’ which is switching my setup with the LG monitor as primary and Eizo as secondary (extended) monitor to using the Eizo monitor as only active monitor. If I’ve switched from 'default' to the 'work' profile and then switch to the ‘tv’ profile (adding the Samsung tv as output, change the resolution to enable cloning of the monitor), the ‘tv’ profile is working. I’ve tried it a couple of times and so far, there has not been any problem.

In short

• default -> tv ==> will not work
• default -> work -> tv ==> is working

Switch directly back from ‘tv’ to ‘work’ or ‘default’ does not have any problems at all.

It seems that there is some kind of ordering required for the changes needed to update the monitor setup. In case of switch from ‘default’ to ‘tv’ profile, this is not handled properly by DisplayFusion.

-- deleted --

Bug is still occuring in DisplayFusion 9.9

Hello,
i think i'm having the same issue with a infinte loop when i switch to a certain monitor profile.
i really hope you'll be able to fix this issue soon. i just bought DF yesterday. but then i noticted it's always crashing when i switch from extended desktop to a single (but mirrored) desktop.
i'm still going to keep it though, because the hotkeys are super useful. but like it is now i still have to use the windows display settings to switch to single desktop setup.

I've tested display fusion 10 beta 18. So far it seems to be able to directly switch to the new profile. I've recreated my profiles again, to avoid any issues cause by the previously installed version.

However, at one occasion after switching display fusion must have gone stuck in some endless loop again and took all available CPU power. Eventually I had to kill the display fusion process once more. At that time, I did not have any logging enabled and unfortunately, I have not been able to reproduce this behavior after enabling logging.

I've managed to grab a log. The logging was enabled & stated after displayfusion went haywire, however you still might be able to detect some kind of endless loop.