Derrick Smith1
3 discussion posts
After 12-48 hours of my computer being on with displayfusion running, the cursor locks up. I can move the mouse around, but nothing highlights (ie. if you hover over a link or something in the taskbar) or responds to a click other than right clicking on the desktop. The only way to fix it is reboot, or use the keyboard to end the display fusion processes.
This behavior is repeatable between 3 separate machines. The program I think may be causing the incompatibility issue is SWare Iron (Chromium based web browser), but I'm not completely sure.
Any thoughts on this? I tried downloading the beta version, but the problem persists. I already suspected Iron was causing the issue, and I suspect it more after the updates notes for the beta v5.1.0 included a bug fix for Chrome.
Strange! Does it just occur after random usage of SWare Iron, or is it possible there's a specific site or plugin (Flash, Java, etc) that might be triggering the issue?
Derrick Smith1
3 discussion posts
I really only keep gmail up for periods of time, and it will occur with just that tab up. I also don't click around on the web much, and don't even have adobe flash installed. The only plugin installed is gmail's pdf reader. Java is installed.
Ok, interesting. I'll try running that browser on a test machine with Gmail open for a few days and hopefully I'll be able to reproduce the same symptoms. I'll keep you posted on what I find out.
Thanks!
I've been running SWare Iron for a while now, and haven't run into this issue at all. If you exit DisplayFusion completely, does this issue still occur after 12-48 hours?
Derrick Smith1
3 discussion posts
Yes.
My first trouble shooting involved restarting the software, then computer. I updated display drivers and W7 updates. Only after that did I post on here.
Rather than uninstalling the program, since I paid for it, I rolled back to 4.0, which hasn't had any of these issues. Unfortunately, it does not have all the same options. I look forward to the next release; hopefully that build will fix my bug.