Error in KernelBase.dll when using nested ItemsRepeater
See original GitHub issueDescribe the bug
When scrolling nested repeaters, scrolling them for a certain amount will result in the following error:
Exception thrown at 0x00007FF84D16361C in ItemsRepeaterExperiments.exe:
Microsoft C++ exception: winrt::hresult_error at memory location 0x000000CF37E7A960.
Steps to reproduce the bug
Steps to reproduce the behavior:
- Open the project in #2284
- Visit the second tab (“Nested selection demo”
- Scroll down using mousewheel or clicking on the inside and pressing page down key
Expected behavior
Not to crash
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (8 by maintainers)
Top Results From Across the Web
Applications Fail to Start with Kernelbase.dll error
The file KernelBase.dll is a DLL file stored in the system folder of Windows operating system. It is created automatically during the ...
Read more >How to Fix Kernelbase.Dll Error In Windows 10/8/7 [Tutorial]
How to Fix Kernelbase. Dll Error In Windows 10/8/7 [Tutorial] KernelBase. dll is the system file of Windows Operating System, which serves ...
Read more >Expander crashes the app when nested with an ...
Describe the bug Having an ItemsRepeater in a Expander will crash the app. Other controls seem to work normally with the expander Regression ......
Read more >Fix - KernelBase.dll crashing error Quickly
Damaged or corrupt KernelBase.dll file. · KernelBase. · Outdated or faulty driver. · Two software using the same KernelBase. · Corrupt Windows ...
Read more >APPCRASH on KERNELBASE.dll Visual Studio 2010 with ...
the error has something to do with kernelbase.dll, but I guess it might not related to windows-kernel, I have removed the tag.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Awesome that you found the root of this issue. Would you like me to look fix this @ranjeshj?
Also is there a way we could add an automatic test for this? The crash itsself can’t be reproduced in a reliable fashion. @StephenLPeters FYI.
Alright, I see. That sounds like a good approach, I will take a look at this tomorrow.