Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report for Bug 57260 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Created attachment 22758 [details]
Stack trace of crash
We've seen a crash happen in our app just on iOS a couple of times when binding happens during a UI update. It looks like the binding tries to get a value and crashes, maybe because the binding context is not there as the UI is changing. It's not reproducible, just has happened a couple of times during testing.
A stack trace is attached - it would be good if a binding operation was able to fail without killing the app.
My initial thought after seeing the crash log is that there might be a handler attached to an object that is still receiving events and trying to access an object that might already be collected.
What version of Xamarin.Forms are you using? Did you start seeing the crash after updating to this version? Have you noticed any patterns of when it does occur, such as after navigating to another page? Also, are you only seeing this on iOS, or on the platforms as well?
That was my thoughts as well - just a bad timing issue, a property change was raised but the object was GC'd before it could get the value.
We've seen it twice so far, just on iOS using 188.8.131.52. It's a rare crash and not reproducible so it may have been an issue with older versions but we didn't see it. It happens when navigating to a different page.
Created attachment 22841 [details]
Stack trace of crash on Android
I'm also seeing a similar crash on Android - same thing, data update when navigating. It's impossible to ensure data is not updated when navigating so it would be good for the binding to not crash the app if the widget is disposed.