We are running into some interesting regressions with mono. We are seeing many failures such as:
Mono v3.12.1 (we have considered moving up to 4.1 or 4.2 but the last time we tested it didn't seem safe to move). Native stacktrace: /home/ubuntu/EventStore-OSS-Ubuntu-v3.2.1/eventstored() [0x609a4f] /home/ubuntu/EventStore-OSS-Ubuntu-v3.2.1/eventstored() [0x5bdecf] /home/ubuntu/EventStore-OSS-Ubuntu-v3.2.1/eventstored() [0x453b19] /lib/x86_64-linux-gnu/libpthread.so.0(+0x10340) [0x7fd9709b7340] /home/ubuntu/EventStore-OSS-Ubuntu-v3.2.1/eventstored() [0x4e6145] [0x40e21ceb] [03041,21,13:43:11.379] Global Unhandled Exception occurred. Object reference not set to an instance of an object [ERROR] FATAL UNHANDLED EXCEPTION: System.NullReferenceException: Object reference not set to an instance of an object at EventStore.Core.Bus.QueuedHandlerAutoReset.ReadFromQueue (System.Object o) [0x00000] in <filename unknown>:0 at System.Threading.Thread.StartInternal () [0x00000] in <filename unknown>:0 note that this isn't a real nre We do not see these regressions in Linux ip-172-31-37-60 3.13.0-46-generic #77-Ubuntu SMP We do see them in Linux ip-172-31-40-115 3.13.0-48-generic #80-Ubuntu SMP Anyone have any ideas how to debug this further? These are not deterministic issues. Cheers, Greg -- Studying for the Turing test _______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
