Re: [mono-android] JavaFinalize and .NET Finalizers

2016-06-23 Thread Jeremy A. Kolb - ARA/NED
-Original Message- > From: monodroid-boun...@lists.ximian.com [mailto:monodroid- > boun...@lists.ximian.com] On Behalf Of Jonathan Pryor > Sent: Tuesday, June 21, 2016 10:07 PM > To: Monodroid for Android > Subject: Re: [mono-android] JavaFinalize and .NET Finalizers > > On

Re: [mono-android] JavaFinalize and .NET Finalizers

2016-06-21 Thread Jonathan Pryor
On Jun 21, 2016, at 3:40 PM, Jeremy A. Kolb - ARA/NED wrote: > We put Activation constructors almost everywhere because they tend to fix > crashes when coming back to an activity. There’s a fine line between a “fix” and “hides the symptoms of the actual problem.” :-) > Plus we allow almost all

Re: [mono-android] JavaFinalize and .NET Finalizers

2016-06-21 Thread Jeremy A. Kolb - ARA/NED
Thanks Jon. Reply is inline. Jeremy > -Original Message- > From: monodroid-boun...@lists.ximian.com [mailto:monodroid- > boun...@lists.ximian.com] On Behalf Of Jonathan Pryor > Sent: Monday, June 20, 2016 10:52 PM > To: Monodroid for Android > Subject: Re: [mono-and

Re: [mono-android] JavaFinalize and .NET Finalizers

2016-06-20 Thread Jonathan Pryor
On Jun 17, 2016, at 9:50 AM, Jeremy A. Kolb - ARA/NED wrote: > I'm investigating https://github.com/MvvmCross/MvvmCross/issues/1343 for a > possible memory leak related to our version of the RecyclerView widget > MvxRecyclerView and have run against an interesting issue. > > When swapping out t