Thanks for getting back to me. I tried the below but no luck I am afraid.
However, I did modify it slightly to run a quick test. Please see below:
loaded = 0;
sender, Telerik.Windows.Controls.ItemStateChangedEventArgs e)
(e.State == ItemState.Recycling)
RadDataBoundListBoxItem container =
(e.State == ItemState.Realizing)
So what this made me notice is that when I got to 40 or so images in my list, as I scrolled up and down through that list, items were recycled as other items were being realized. Thus meaning the loaded value stayed at around 40 items, such that there was only ever 40 realized items in the list.
However, when I then completed another update to get more items (which adds additional range to the ObservableCollection items source from a list which has all the items), the event fired all the realized items in a row before attempting to recycle other items, meaning that I then had about 60 items in the list, at which point it crashed before it could load all the newly added items.
I imagine that this is probably the issue? It seems that when the item source is updated, all the newly added items are realized first before the list box attempts to recycle other items. Which would make sense why higher end devices are able to go a while longer before crashing, if not, not crashing at all.
Could this be the reason?