I just installed the 4.2 kernel and we get the same issue in our code.
Interestingly, I wasn't able to reproduce it against 4.1 or 4.2 using the
repro test case linked to from that bug.
Running 4.09 though, all seems well.
Any idea why the fix got rolled back? And when/whether it will be fixed
Ah, of course, thank-you!! We had seen this in the past but not for a while
now. It resurfaced when we moved to a new instance, which still had the old
kernel. D'oh. Super unfortunate that this appears to be back in 4.1 :(.
On 27 November 2015 at 23:10, Matt Calder wrote:
>
Any idea if it's been fixed again in 4.2?
On 27 November 2015 at 23:26, River Satya wrote:
> Ah, of course, thank-you!! We had seen this in the past but not for a
> while now. It resurfaced when we moved to a new instance, which still had
> the old kernel. D'oh. Super
River,
We see seg-faults in multi-threaded code on Ubuntu 14.04 and 14.10. These
can be reproduced relatively easily. We believe it is this bug:
https://bugzilla.xamarin.com/show_bug.cgi?id=29692
The discussions there will lead you to some discussions about kernel
versions. We still see this
Stack trace flavour 3:
--
:Stacktrace:
-
- at <0x>
- at (wrapper managed-to-native) System.Delegate.CreateDelegate_internal
(System.Type,object,System.Reflection.MethodInfo,bool)
- at System.Delegate.CreateDelegate
(System.Type,object,System.Reflection.MethodInfo,bool,bool)