-
Notifications
You must be signed in to change notification settings - Fork 693
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Occasional crashes when using ScrollView to wrap nested ItemsRepeater #9345
Comments
Hi I'm an AI powered bot that finds similar issues based off the issue title. Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one. Thank you! Open similar issues:
Closed similar issues:
|
I found a solution by replacing the first ItemsRepeater with a ListView. It seems that multiple ItemsRepeater cannot be directly nested. According to Microsoft's official documentation, it is recommended that ItemsRepeater only be used for data display. |
@wky214269273 thanks for reporting and the details. Is this the smallest repro to cause it to crash ? Would it still crash without the Expander etc in the template. If you are able to provide a smaller/minimal repro that would be useful. Thanks! |
I tried this xaml markup
with this code behind:
I could not repro the layout cycle in 125% and 150% DPI, for the WinAppSDK 1.7 release. |
Describe the bug
When using a ScrollView to wrap nested ItemsRepeater, there is an occasional Layout Cycle Detected exception. There is also a strange issue where when I use Debug to debug and try to catch the exception, it never triggers, but when I run the program individually, both Debug and Release builds trigger it.
Steps to reproduce the bug
Refer to the following code. As long as you swipe, there is a high probability of triggering. Also, it seems to be related to DPI. I have not triggered it when using 100% DPI on my desktop, but my laptop has a high trigger rate when using 150% DPI.
The text was updated successfully, but these errors were encountered: