https://www.displayfusion.com/Discussions/View/edge-with-df/?ID=f7a19052-3999-4df2-b0de-082b38f08009

Still suffers from this issue. Edge windows appear on both taskbars regardless of settings. Only Edge, no other application.

Dec 8, 2020 (modified Dec 8, 2020)  • #2

Beta 7 worked just fine for me but beta 8 keeps crashing constantly. It's crashed at least 10 times so far today. I'm gonna revert to the stable version for now.

EDIT: since it happened once more before I reverted back I noticed it mostly crashes when I use the button to reduce windows to tray icons. This last crash was caused by using it with Thunderbird 68.x.

Dec 8, 2020 (modified Dec 8, 2020)  • #3

for me beta 7 crashed and saw the beta 8 update that indicated that was fixed. I was stoked. Updated to beta 8 but still crashing. rip!

Dec 8, 2020  • #4

9.7.1 Beta 8 still crashing for me as well. I have not noticed a pattern yet.

Latest crash: No action when I clicked a "move & size" TitleBar button. Moved mouse to DF taskbar button, which disappeared once over the DF icon.

Windows 10 Enterprise 1909 Build 18363.1198
********* 12/9/2020 - Added Note *********
Latest crash: No action when I clicked a "move & size" TitleBar button. Moved mouse to DF taskbar button, which disappeared once over the DF icon.

Faulting application name: DisplayFusion.exe, version: 9.7.0.108, time stamp: 0x5fce4a47
Faulting module name: clr.dll, version: 4.8.4250.0, time stamp: 0x5f2a059c
Exception code: 0xc00000fd
Fault offset: 0x00000000001bbc7e
Faulting process id: 0x7240
Faulting application start time: 0x01d6ce38ee90e300
Faulting application path: C:\Program Files (x86)\DisplayFusion\DisplayFusion.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: bd2736ae-687d-45c3-9276-36b285c9dfbe
Faulting package full name:
Faulting package-relative application ID:
********* 12/10/2020 - Added Note *********
Latest crash: Crashed right after startup. Same exact Event error.
*Pic Attached*
Faulting module path: C:\Windows\Microsoft.NET\Framework64\ v4.0.30319\clr.dll

• Attachment: 2020-12-09-DF-Error.png [257,355 bytes]

• Attachment: 2020-12-10-DF-Error.png [193,897 bytes]

Dec 9, 2020 (modified Dec 10, 2020)  • #5

Hello,

We are aware of the crashes still persisting with the latest beta. We are looking into it, and we'll be sure to let you know when we have any news on it in the future.

Thanks!

Dec 9, 2020  • #6

Yes. Still crashing for no reason at all.

Dec 9, 2020  • #7

Hello,

This issue should be fixed up in the latest beta, available here: https://www.displayfusion.com/Download/Beta. Please let me know if you still run into any trouble after updating.

Thanks!

Dec 10, 2020  • #8

issue still there for me, after upgrading to b9. Just had another crash after system running fine for ~4 hours (and it had even been rebooted after the upgrade)

Dec 11, 2020  • #9

Beta 9 works just fine for me so far.

Dec 11, 2020  • #10

Hello,

@chb80 Are the crashes happening when you move windows around?

Thanks!

Dec 11, 2020  • #11

I will try to check. Problem is, the time I notice it crashed (titlebar buttons become black, taskbar is no longer responsive) is most likely not the time it actually does.
But I move windows all day, so that might be related. When I have a hint, I will reply back.

Dec 11, 2020  • #12

Hello,

Sounds good, in the meantime, could you send me over a debug log if it crashes again? Here are the steps:

• On the DisplayFusion Settings > Troubleshooting tab, change the Logging drop-down to "L1: Log Minimal" and click Apply
• Reproduce the issue and note the time so we'll know where to check in the log file
• Click the "Export Info to File" button on the Settings > Troubleshooting tab
• Reply with the file attached
• Disable debug logging after sending the log

Thanks!

Dec 11, 2020  • #13

Debug log attached. I noticed the crash and killed the application at around 11:52.

Edit: Added a second one, since it just crashed again, noticed at 13:07

• Attachment [protected]: DisplayFusionDebugInfo 202012151202.zip [204,078 bytes]

• Attachment [protected]: DisplayFusionDebugInfo 202012151313.zip [177,748 bytes]

Dec 15, 2020 (modified Dec 15, 2020)  • #14

Hello,

Thanks for sending those over. Which beta did it start crashing for you?

Thanks!

Dec 15, 2020  • #15

issues started with Beta 7 as far as I remember

Dec 15, 2020  • #16

Hello,

We've just released beta 10. Can you update and enable the "Logging: Disable Log Buffering" advanced setting, restart Display Fusion, and then send over another log when it crashes?

Thanks!

Dec 17, 2020  • #17

there you go, crash detected 10:32
(Note that I have now afterwards again, same as the days before, downgraded to non-Beta, since it crashes multiple times per hour)

• Attachment [protected]: DisplayFusionDebugInfo.zip [252,769 bytes]

Dec 18, 2020 (modified Dec 18, 2020)  • #18

If you go to the "C:\Users\username\AppData\Local\Binary Fortress Software\DisplayFusion\CrashDumps" folder, are there any files in there?

28 days ago  • #19

Folder does not even exist. There is a "Binary_Fortress_Software" folder (with underscores), but rather old and with no CrashDumps anywhere inside its sub structure.

28 days ago  • #20

Ok, thanks for checking that. It sounds like it's not actually crashing but rather hung or dead-locked. The next time this happens, could you do the following?

• On the Windows Task Manager > Details tab, right-click DisplayFusion.exe and choose "Create dump file"
• When the dump file is created it will show the path and file name in a dialog box
• Zip the file
• Send us a support request through the DisplayFusion Settings window (Help > Support Request) but don't attach the dump file as it will be too big. Just send in the request and we will send further instructions on how to send the process dump

Thanks!

26 days ago  • #21

ok, did that when it last crashed yesterday. Hope they can find something in it

I noticed today that 9.7.1 (non-beta) is available. Was there anything further 'repaired' compared to the latest betas that would help with my issues? Or will 9.7.1 just introduce the same trouble to the regular version as well (in which case I would refrain from updating until my problem has been found)?

21 days ago  • #22

Got the request and have just responded.

Thanks!

20 days ago  • #23