Bug: Unhandled Windows.UI.Xaml.LayoutCycleException from ProgressBar with Large Maximum

[Brian-at-Baebies]

Describe the bug

MCRE example attached.

In summary:

ProgressBar.Maximum set to some high value (3000, e.g.), and Value set to nearly 100% (2998, e.g.), causes an unhandled Windows.UI.Xaml.LayoutCycleException.

MCRE_LayoutCycleDetected.zip

Steps to reproduce the bug

1. Build the attached MCRE solution
2. Run the solution
3. Click the "Set" button
4. Observe unhandled exception

May need to play around with "Value" to hit it (in my testing, 2999 did not cause the exception, but 2998 did).

Expected behavior

ProgressBar reflects Value and Maximum; no LayoutCycleException thrown

Screenshots

No response

NuGet package version

None

Windows version

Windows 10 (21H2): Build 19044

Additional context

Actual Windows version is Windows 10 Professional 22H2 Build 19045.4291 (not an option in the drop-down above)
Ms.NETCore.UniversalWindowsPlatform is version 6.2.14 (latest stable as of this writing)

[codendone]

There is a fix for this issue in WinUI3. There are no plans to try to bring the fix to WinUI2.

Your example includes Margin="5" on the ProgressBar. Part of the issue is ProgressBar doesn't handle Margin properly, so removing Margin from this element (and setting it on an ancestor panel, if needed) will hopefully be sufficient for you to avoid this issue.