microsoft / microsoft/microsoft-ui-xaml
ItemsRepeater crashes when opened inside a new window in UWP
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 8.4k
- Forks
- 942
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 105
Description
Describe the bug
When a control that contains an ItemsRepeater is opened in a new window, the application crashes immediately. This happens even if the ItemsRepeater has no data and no templates applied.
Why is this important?
This issue is serious because it breaks a basic and valid use case. Our application needs to open views in separate windows, and those views often contain an ItemsRepeater. The crash prevents us from using multi window scenarios in any meaningful way. Even the simplest ItemsRepeater with no data causes the window to fail, which blocks core navigation and limits the entire feature set. This affects end users directly since they cannot open or work with content in a new window without the app closing.
Steps to reproduce the bug
- Create UWP app
- Add Microsoft.UI.Xaml Nuget package
- Create a ItemsRepeater in MainPage.xaml
- Open that MainPage in New Window
Actual behavior
No response
Expected behavior
No response
Screenshots
NuGet package version
WinUI 2 - Microsoft.UI.Xaml 2.8.7
Windows version
Windows 11 (23H2): Build 22631
Additional context
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Use the attached ItemsRepeaterCrash_NewWindow.zip to reproduce the crash in the UWP setup described. Start with MainPage.xaml and the step that opens the page in a new window, then collect the failure details and trace the ItemsRepeater initialization path. Done means an empty ItemsRepeater no longer crashes when its containing page opens in a new window.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100