https://www.displayfusion.com/Discussions/RSS/?TopicID=4fd3d1ca-2952-49fd-8d2a-431e4369ec89 DisplayFusion RSS: Force close in 4.0.1 beta6 Tue, 07 Apr 2026 17:01:07 GMT en hourly 1 https://www.displayfusion.com/Discussions/RSS/?TopicID=4fd3d1ca-2952-49fd-8d2a-431e4369ec89 https://www.displayfusion.com/Discussions/View/force-close-in-401-beta6/?ID=4fd3d1ca-2952-49fd-8d2a-431e4369ec89#15 Fri, 22 Jun 2012 23:30:07 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/force-close-in-401-beta6/?ID=4fd3d1ca-2952-49fd-8d2a-431e4369ec89#15 DisplayFusion Ok, last update to this thread

We've now posted Beta 7, so for anyone who still has hanging/crashing issues, please give it a try and post the results in this new topic: http://www.displayfusion.com/Discussions/View/4-1-beta-6-testing-results/?ID=4e1b763b-36b1-4ac9-9b66-308b548be6b5

Thanks! ]]> https://www.displayfusion.com/Discussions/View/force-close-in-401-beta6/?ID=4fd3d1ca-2952-49fd-8d2a-431e4369ec89#14 Fri, 22 Jun 2012 20:59:36 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/force-close-in-401-beta6/?ID=4fd3d1ca-2952-49fd-8d2a-431e4369ec89#14 DisplayFusion Hi all,

We just found a bit of a show-stopping bug in Beta 6, so we've had to pull it for now. We'll be fixing it up, and hopefully will have Beta 7 posted soon.

Sorry for the inconvenience! ]]> https://www.displayfusion.com/Discussions/View/force-close-in-401-beta6/?ID=4fd3d1ca-2952-49fd-8d2a-431e4369ec89#13 Fri, 22 Jun 2012 18:39:01 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/force-close-in-401-beta6/?ID=4fd3d1ca-2952-49fd-8d2a-431e4369ec89#13 DisplayFusion Hi all,

DisplayFusion 4.1 Beta 6 (http://www.displayfusion.com/Download/Beta/) is now available, and we're very confident that we've fixed up the issues with DisplayFusion hanging/crashing.

Since there are some people who have been running fine already with earlier betas, and some who are still having issues with DisplayFusion hanging/crashing in Beta 5, I've started a new topic for the results of the Beta 6 testing.

http://www.displayfusion.com/Discussions/View/4-1-beta-6-testing-results/?ID=4e1b763b-36b1-4ac9-9b66-308b548be6b5

I'm going to lock this topic, so if anyone who's still having hanging/crashing issues with Beta 5 could update to Beta 6, and then post the results in the topic mentioned above, that would be much appreciated

Thanks! ]]> https://www.displayfusion.com/Discussions/View/force-close-in-401-beta6/?ID=4fd3d1ca-2952-49fd-8d2a-431e4369ec89#12 Fri, 15 Jun 2012 19:35:56 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/force-close-in-401-beta6/?ID=4fd3d1ca-2952-49fd-8d2a-431e4369ec89#12 DisplayFusion Thanks! Did that crash happen with the tray icons still disabled? ]]> https://www.displayfusion.com/Discussions/View/force-close-in-401-beta6/?ID=4fd3d1ca-2952-49fd-8d2a-431e4369ec89#11 Thu, 07 Jun 2012 23:48:49 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/force-close-in-401-beta6/?ID=4fd3d1ca-2952-49fd-8d2a-431e4369ec89#11 DisplayFusion Got the first force stop since last time after updating to beta 4.1.0 beta 3.

Attached is the log - this time I made sure it was set to all lines, so I hope that helps. ]]> https://www.displayfusion.com/Discussions/View/force-close-in-401-beta6/?ID=4fd3d1ca-2952-49fd-8d2a-431e4369ec89#10 Wed, 06 Jun 2012 21:30:14 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/force-close-in-401-beta6/?ID=4fd3d1ca-2952-49fd-8d2a-431e4369ec89#10 DisplayFusion I've made some excellent progress today on this issue. Can you follow-up once Beta 3 has been released tomorrow (Thursday)? Thanks! ]]> https://www.displayfusion.com/Discussions/View/force-close-in-401-beta6/?ID=4fd3d1ca-2952-49fd-8d2a-431e4369ec89#9 Mon, 04 Jun 2012 21:44:46 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/force-close-in-401-beta6/?ID=4fd3d1ca-2952-49fd-8d2a-431e4369ec89#9 DisplayFusion Removing tray icons seems to have eliminate the problem. ]]> https://www.displayfusion.com/Discussions/View/force-close-in-401-beta6/?ID=4fd3d1ca-2952-49fd-8d2a-431e4369ec89#8 Wed, 30 May 2012 12:52:13 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/force-close-in-401-beta6/?ID=4fd3d1ca-2952-49fd-8d2a-431e4369ec89#8 DisplayFusion Sounds good, thanks voo! ]]> https://www.displayfusion.com/Discussions/View/force-close-in-401-beta6/?ID=4fd3d1ca-2952-49fd-8d2a-431e4369ec89#7 Tue, 29 May 2012 18:11:14 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/force-close-in-401-beta6/?ID=4fd3d1ca-2952-49fd-8d2a-431e4369ec89#7 DisplayFusion After the crash I set it to important only and only changed it after your follow up post - so maybe I didn't accept the change correctly.

It's now set to all lines and I've removed the icons. ]]> https://www.displayfusion.com/Discussions/View/force-close-in-401-beta6/?ID=4fd3d1ca-2952-49fd-8d2a-431e4369ec89#6 Tue, 29 May 2012 14:13:31 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/force-close-in-401-beta6/?ID=4fd3d1ca-2952-49fd-8d2a-431e4369ec89#6 DisplayFusion Thanks! Did you have the debug logging set to Logging: All Lines? It looks like it was only set to Logging: Important Only.

From the log, the last thing that happened was the system tray icons on the DF taskbar updated, which may or may not be related. Would you be able to make sure the debug logging is set to All Lines, then disable the tray icons on the DF taskbar (right-click the taskbar, navigate to Multi-Monitor Taskbar > System Tray > Show/Hide icons), and see if it crashes again? Please send the updated debug log if it does crash again.

Thanks! ]]> https://www.displayfusion.com/Discussions/View/force-close-in-401-beta6/?ID=4fd3d1ca-2952-49fd-8d2a-431e4369ec89#5 Mon, 28 May 2012 23:03:17 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/force-close-in-401-beta6/?ID=4fd3d1ca-2952-49fd-8d2a-431e4369ec89#5 DisplayFusion Turns out, we were.. umn "lucky"? Well anyhow the logs are attached this time ]]> https://www.displayfusion.com/Discussions/View/force-close-in-401-beta6/?ID=4fd3d1ca-2952-49fd-8d2a-431e4369ec89#4 Mon, 28 May 2012 19:03:12 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/force-close-in-401-beta6/?ID=4fd3d1ca-2952-49fd-8d2a-431e4369ec89#4 DisplayFusion Ok, no worries at all! ]]> https://www.displayfusion.com/Discussions/View/force-close-in-401-beta6/?ID=4fd3d1ca-2952-49fd-8d2a-431e4369ec89#3 Mon, 28 May 2012 19:02:10 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/force-close-in-401-beta6/?ID=4fd3d1ca-2952-49fd-8d2a-431e4369ec89#3 DisplayFusion Have done that, but as I said, the crashes are quite rare - the PC has been running since beta4 without any crashes apart from this one, so that may take some time. ]]> https://www.displayfusion.com/Discussions/View/force-close-in-401-beta6/?ID=4fd3d1ca-2952-49fd-8d2a-431e4369ec89#2 Mon, 28 May 2012 18:24:57 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/force-close-in-401-beta6/?ID=4fd3d1ca-2952-49fd-8d2a-431e4369ec89#2 DisplayFusion Thanks! Could you enable debug logging on the Troubleshooting tab (set it to Logging: All Lines), and attach a copy of the debug logs the next time it crashes?

Thanks! ]]> https://www.displayfusion.com/Discussions/View/force-close-in-401-beta6/?ID=4fd3d1ca-2952-49fd-8d2a-431e4369ec89 Mon, 28 May 2012 13:25:34 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/force-close-in-401-beta6/?ID=4fd3d1ca-2952-49fd-8d2a-431e4369ec89 DisplayFusion The problem happens only quite rarely it seems (first time for me since beta4) and I didn't have logging enabled. No logging, but I did create minidumps of the exe itself and the hook, so that should help debugging the problem.

To be exact I ran ".dump /ma" under windbg. Since those files are rather large I can't upload them directly here - and since I don't want to publish dumps that may contain sensitive data, I'm going for the simple solution of uploading the data somewhere and posting the link as a private attachment (including the troubleshooting information). ]]>