-
Notifications
You must be signed in to change notification settings - Fork 32
Description
Platform (please complete the following information):
- OS: [iOS/Both?]
- Device: [iPhoneSimulator/iPhoner/...]
- Sdk vervion: [iOS 15.2]
- .NET MAUI: [8.0.10-nightly.10215]
Describe the bug
When I use an ObservableRangeCollection with the Sharpnado CollectionView, which has any kind of NotifyCollectionChangedAction.Reset, e.g. in an .AddRange(..., NotifyCollectionChangedAction.Reset), I see rising memory consumption and finally a Crash of my App on my real device.
I am not sure if it is the Sharpnado CollectionView, but I just wanted to mention it in case there is an issue.
I described this issue also on the .NET MAUI Issue page more detailled: Rising Memory Consumption leading to crashing App after a while when Utilizing NotifyCollectionChangedAction.Reset in ObservableRangeCollection
To Reproduce
Steps to reproduce the behavior:
- Use
.AddRange(..., NotifyCollectionChangedAction.Reset)on anObservableRangeCollectionthat is bound to a (Sharpnado)CollectionViewand see the memory consumption rising. This can also be observed when the same option is used in a.RemoveRange(.., NotifyCollectionChangedAction.Reset)call a couple of times. - Animation and example project can be found on the corresponding issue: Rising Memory Consumption leading to crashing App after a while when Utilizing NotifyCollectionChangedAction.Reset in ObservableRangeCollection
- As I said, I am not sure if the Sharpnado
CollectionViewis involved in there, but just mentioned it in case
Exceptions (if applicable)
There is no StackTrace available
Screenshots (if applicable)
If applicable, add screenshots to help explain your problem.