Chrome v69 beta ignores DF monitor splits

WARNING: You currently have Javascript disabled!
This website will not function correctly without Javascript enabled.

mkizer

19 discussion posts

After updating to the latest Chrome v69 beta, I've noticed that it no longer recognizes DF monitor splits and instead maximizes to the entire monitor. It also will not move/maximize to other monitors, but a move by itself seems to work.

It could just be something new in this release of Chrome. Is any one else having issues with Chrome?

Aug 16, 2018 • #1

I've just tested with Chrome Canary, which is currently on 70.0.3525.0 and it seems to work for me without issues. Could you attach a copy of your troubleshooting info?

Open the Settings > Troubleshooting tab
Click the "Export Info to File" button
Reply with the file attached

Thanks!

Aug 17, 2018 • #2

mkizer

19 discussion posts

Thanks.

• Attachment [protected]: DisplayFusion Backup (2018-08-17 @ 08-41, 9.3.0.0, YYZ).reg [139,234 bytes]

• Attachment [protected]: DisplayFusionDebugInfo.zip [27,633 bytes]

Aug 17, 2018 • #3

Thanks! Everything looks ok there! Could you send over a full debug log? Here are the steps:

On the DisplayFusion Settings > Troubleshooting tab, change the Logging drop-down to "L1: Log Minimal" and click Apply
Reboot, then launch Chrome and try to maximize it to a split
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!

Aug 17, 2018 • #4

mkizer

19 discussion posts

You got it.

• Attachment [protected]: DisplayFusionDebugInfo2.zip [96,303 bytes]

Aug 17, 2018 • #5

Thanks! Two more questions:

Could you send another debug log, but this time, capture the log while maximizing an application that does respect the splits?
Just to double-check, have you done a full reboot since updating to the latest Chrome beta?

Thanks!

Aug 17, 2018 • #6

mkizer

19 discussion posts

Sure thing. Here it is while using notepad.

Rebooted prior to running each test.

• Attachment [protected]: DisplayFusionDebugInfo3.zip [168,571 bytes]

Aug 17, 2018 • #7

Naidu

20 discussion posts

Display Fusion Is not supported v69. Please see the screenshot below.

• Attachment [protected]: Capture.PNG [53,793 bytes]

Aug 20, 2018 • #8

@mkizer: I'm stumped here! If you drag the Chrome window, does the DisplayFusion titlebar button stick with it, or does it lag behind for a second or two?

@Naidu: You can ignore that warning in Chrome. Chrome is showing that now for any applications that use global hooks, regardless of whether or not they actually cause issues.

Aug 20, 2018 • #9

mkizer

19 discussion posts

Huh, I hadn't really noticed that before, but it does lag behind for a second or so.

Aug 20, 2018 • #10

Ok, thanks for trying that out. It definitely sounds like Chrome isn't getting hooked but I can't figure out why that might be.

Could you do the following?

Run Process Explorer
On the toolbar, click the 5th icon from the left (should say "Show Lower Pane")
On the toolbar, click the 6th icon from the left (should say "View DLLs" in the tooltip)
Click on chrome.exe
In the lower pane, is "AppHook64_{guid}.dll" listed?

Aug 21, 2018 • #11

mkizer

19 discussion posts

Yes, AppHook64 is loaded.

• Attachment [protected]: 2018-08-21 13_01_45-Process Explorer - Sysinternals_ www.sysinternals.com [YYZ_Michael].png [79,910 bytes]

Aug 21, 2018 • #12

mkizer

19 discussion posts

I just upgraded to DF 9.4 beta 1 and the Chrome issue appears to be resolved.

It may not have been directly addressed, but perhaps the install process fixed something that went a bit sideways.

I'll let you know if the issue pops up again.

Aug 23, 2018 • #13

Wow, that's great news I guess! Thanks for following-up, and definitely let me know if you run into any more trouble.

Thanks!

Aug 24, 2018 • #14