Window glitches when dragging app between monitors with different scaling

[Felicity-R]

Description

Dragging a Maui app between different monitor causes visual glitches and eventually stops responding. See attached video to see what I mean: screen-capture.webm. In the video I'm just recording my 2nd monitor; the laptop screen is below it so that's where the app is when I drag it off screen below. In the end I need to ctrl+alt+delete to get to the task manager and force close it because everything stops responding.

Steps to Reproduce

1. Have a dual-monitor setup
2. Set custom scaling on monitor in the display settings. e.g. I have my laptop scaling set to 125% and a secondary monitor with scaling at 100%. (If I change the laptop to also be 100% scaling then the bug does not occur).
   
3. Create a new app from the .Net MAUI App template (using .Net7)
4. Launch the app
5. Drag the app from one monitor to the other. If it's still behaving normally, drag it back.

Expected results:
You can freely move the app around and it will work fine.

Actual results:
After moving from one monitor to the other a few times, it will break. Sometimes the app window flashes around wildly, sometimes just the edge of the window twitches - see video in description.

Link to public reproduction project repository

Can repro in the Maui template app

Version with bug

7.0 (current)

Last version that worked well

Unknown/Other

Affected platforms

Windows

Affected platform versions

Windows 10 19043.2251

Did you find any workaround?

Don't use different scaling

Relevant log output

No response

[drasticactions]

If you try this in a WinUI application without MAUI, what happens?

[ghost]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[Felicity-R]

Good question. I tried with a new app from the "Blank App, Packaged (WinUI 3 in Desktop)" template, changed it to .net7 to match the Maui project and was not able to reproduce the issue there. I also tried adding a ScrollViewer and some TextBoxes there and still no repro.
Then I pared down the Maui app, removing all the controls from the main page so it was just a blank page, and the Maui app still had the issue.

[DerPate2010]

I see the same behavior on my machine. One display is at 200% and a second one at 150%. I see different kinds of flickering effects and the content seems to toggle between both DPI settings (= sizes).

Based on the behavior my assumption is, that the MAUI window is doing some resizing strategy before the user releases the mouse cursor on the second screen

1. It seems as if the window is being resized as a reaction to the message from Windows when moving to the second screen.
2. As a result of the resizing the main part of the smaller window is now back on the first screen. =>
3. Windows is sending a message to scale to this size.
4. Maui rescales to the larger window and the main part of the window is on the second screen again =>
5. goto 1

When I break the execution I always see stack trace like this:

[jerry-synap]

I have the same issue with Maui Blazor App. One monitor is at 125% and the other is at 100%. When I drag the Maui app from the 125% monitor to the 100%, it gets stuck halfway, flickering as if re-rendering but the app itself is unresponsive and has to be killed off. On the other hand, if I drag from 100% to 125% the problem does not show up. As long as the app starts in a 100% scaling monitor it seems okay to be dragged afterward but not if it starts up in a 125% scaled monitor. You cannot drag back from 125% to 100%.

[LFXA]

I have the same issue with Maui Blazor App. any update?

[drasticactions]

#14597 (comment)

This mentions the possible issue. Calculating the Width, Height, X, and Y could be causing it to redraw and freak out.

[salarcode]

Addition to my comment #14597 (comment)
If I add this line to the method, we can see that this FrameChanged method is in a hot path

if (_batchFrameUpdate > 0)
{
	Debug.WriteLine($"_batchFrameUpdate={_batchFrameUpdate}, frame={frame}");
}

Like this:

I will get this when I move MAUI window from a monitor with 150% scaling to another one with 100% scaling:

_batchFrameUpdate=1, frame={X=-279 Y=160 Width=797 Height=1211}
_batchFrameUpdate=2, frame={X=-279 Y=160 Width=797 Height=807}
_batchFrameUpdate=2, frame={X=-186 Y=106.66666412353516 Width=797.3333129882812 Height=1210.6666259765625}
_batchFrameUpdate=3, frame={X=-186 Y=160 Width=797.3333129882812 Height=1210.6666259765625}
_batchFrameUpdate=1, frame={X=-519 Y=151 Width=797 Height=1211}
_batchFrameUpdate=2, frame={X=-519 Y=151 Width=797 Height=807}
_batchFrameUpdate=2, frame={X=-519 Y=151 Width=797 Height=1211}
_batchFrameUpdate=1, frame={X=-519 Y=151 Width=531 Height=1211}
_batchFrameUpdate=1, frame={X=-519 Y=151 Width=531 Height=807}

It seems to me that updating bindable properties in such hot path is not a good idea.

.

[salarcode]

maui/src/Controls/src/Core/HandlerImpl/Window/Window.Impl.cs

Lines 209 to 212 in 48d0294

	X = frame.X;
	Y = frame.Y;
	Width = frame.Width;
	Height = frame.Height;

These lines are causing performance regression imo

@jonathanpeppers pinging for help

[jonathanpeppers]

The picture of a stack trace above shows this is called:

maui/src/Core/src/Platform/Windows/WindowExtensions.cs

Line 26 in 2b823f8

public static void UpdatePosition(this UI.Xaml.Window platformWindow, IWindow window)

Hoping this was profiled in Release mode, but can you share your profiler data here?

So, is this what is happening?

1. User drags window
2. Windows APIs -> tells MAUI the position changed
3. MAUI OnPropertyChanged() -> calls Windows API to update position
4. Repeat in a loop?

These lines are causing performance regression imo

Regression from what? .NET 6?

[salarcode]

Unfortunately i didn't save that file, wasn't expecting it be needed. And yes it was in Release mode.

Here is another run I did in Release mode.
What I did is just run Maui.Controls.Sample and move the window between two monitors with different scaling as I've mentioned before.
At the end I managed to glitch the app and it was stuck and unresponsive like this :

Maui.Controls.Sample_Xl8BmnifAD.mp4

Here is the profile session for above :

Report20230421-0905.zip

Regression from what? .NET 6?

I think based on #4942 yes.

[rmarinho]

Sorry but we have to revert the PR that fixes this issue. We are working in improving the related fix to be merged on main.
Thanks.