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 on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
When using WeakReferences, one should be careful to not rely on IsAlive = true. If this property returns false, then the object has been GC'ed for sure. If it returns true, however, it could either be alive with a strong reference or marked for garbage collection.
There are several places in XF source code where IsAlive is used when it is true. In my opinion, these should be fixed and you should probably create some kind of VS macro to guard against future mistakes.
That said, there might be true use cases when IsAlive is true and you want to run some kind of code before an object is GC'ed. However, this seems to be more of an edge case than just checking the Target property.