From owner-freebsd-mono@freebsd.org Sun May 8 21:00:28 2016 Return-Path: Delivered-To: freebsd-mono@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4C71DB33E25 for ; Sun, 8 May 2016 21:00:28 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 3C88E1A3B for ; Sun, 8 May 2016 21:00:28 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 3BF02B33E20; Sun, 8 May 2016 21:00:28 +0000 (UTC) Delivered-To: mono@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3BA23B33E1D for ; Sun, 8 May 2016 21:00:28 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 17E0F1A36 for ; Sun, 8 May 2016 21:00:28 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u48L015U058769 for ; Sun, 8 May 2016 21:00:27 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201605082100.u48L015U058769@kenobi.freebsd.org> From: bugzilla-noreply@FreeBSD.org To: mono@FreeBSD.org Subject: Problem reports for mono@FreeBSD.org that need special attention Date: Sun, 08 May 2016 21:00:27 +0000 X-BeenThere: freebsd-mono@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Mono and C# applications on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 May 2016 21:00:28 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- New | 206593 | lang/mono: fix kevent-based file system monitor o 1 problems total for which you should take action. From owner-freebsd-mono@freebsd.org Thu May 12 16:41:49 2016 Return-Path: Delivered-To: freebsd-mono@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C0F6FB37EE6 for ; Thu, 12 May 2016 16:41:49 +0000 (UTC) (envelope-from bounce+8cc18d.d053-freebsd-mono=freebsd.org@markheppner.com) Received: from mail-s91.mailgun.info (mail-s91.mailgun.info [184.173.153.219]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 87C1E1318 for ; Thu, 12 May 2016 16:41:49 +0000 (UTC) (envelope-from bounce+8cc18d.d053-freebsd-mono=freebsd.org@markheppner.com) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=markheppner.com; q=dns/txt; s=krs; t=1463071307; h=Content-Type: To: From: Subject: Message-ID: Date: MIME-Version: Sender; bh=XVs9GbHgcWs4e6ma1KJTzO1zrVqJFUAhkoJE2mzApxk=; b=ccU/H8CDed0JYDofThCJsnzjwjvta95PsZqzuSYhCD3X38p3esc1F63A6rjiIj0eKuF2pKyR DI6xogdSujy6dQ40rr0qRoEPLnF2azyW+jDmUC12mkLYCFhIgEZEk2Uar0VbLKN9jEP+eZDK 1eaD+HRp4hw5ajccDkXXp57Vh7g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=markheppner.com; s=krs; q=dns; h=Sender: MIME-Version: Date: Message-ID: Subject: From: To: Content-Type; b=hSg/8LhCnHHKSRI9CTcfVHD3n3EhCBESmkxDjVTe5dUEDQmKqWAtwBZLmvDGx+AJbfsXJ9 2Q4ReWsugcsX7s3wvW4zOOv0y27JVF7lVPtmA/TQYjcZkjfpKMtnpfJKTMCsf/L3A6qzmDsw NQM3WGpy2P1F2ohMFGMq+RcGaXf7Q= Sender: freebsd@markheppner.com X-Mailgun-Sid: WyJhNGEyOSIsICJmcmVlYnNkLW1vbm9AZnJlZWJzZC5vcmciLCAiZDA1MyJd Received: from mail-wm0-f49.google.com (mail-wm0-f49.google.com [74.125.82.49]) by mxa.mailgun.org with ESMTP id 5734ac3a.100bcaf0-in6; Thu, 12 May 2016 16:15:54 -0000 (UTC) Received: by mail-wm0-f49.google.com with SMTP id n129so266072784wmn.1 for ; Thu, 12 May 2016 09:15:54 -0700 (PDT) X-Gm-Message-State: AOPr4FXlwOhUNweo6ibNpSd02qv5mo53TypvifGAzje3i7uHrpVJN0r5BvxcmctL007+5Jg3HhY7bnuqugYfBQ== MIME-Version: 1.0 X-Received: by 10.194.104.138 with SMTP id ge10mr10285468wjb.85.1463069753355; Thu, 12 May 2016 09:15:53 -0700 (PDT) Received: by 10.28.167.203 with HTTP; Thu, 12 May 2016 09:15:53 -0700 (PDT) Date: Thu, 12 May 2016 12:15:53 -0400 X-Gmail-Original-Message-ID: Message-ID: Subject: Sonarr/Mono crash with SIGSEGV on 10.3-STABLE From: Mark Heppner To: freebsd-mono@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-mono@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Mono and C# applications on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 May 2016 16:41:49 -0000 I was able to run sonarr-2.0.0.3953 on mono-4.2.3.4 on 10.2-STABLE. After upgrading to 10.3-STABLE, the program now crashes with this stacktrace: [Info] Bootstrap: Starting Sonarr - /usr/local/share/sonarr/NzbDrone.exe - Version 2.0.0.3953 [Info] AppFolderInfo: Data directory is being overridden to [/usr/local/sonarr] Stacktrace: at <0xffffffff> at (wrapper managed-to-native) System.Diagnostics.Process.ProcessName_internal (intptr) <0xffffffff> at System.Diagnostics.Process.get_ProcessName () <0x00047> at (wrapper remoting-invoke-with-check) System.Diagnostics.Process.get_ProcessName () <0xffffffff> at NzbDrone.Common.EnvironmentInfo.RuntimeInfoBase.InternalIsProduction () <0x00080> at NzbDrone.Common.EnvironmentInfo.RuntimeInfoBase..cctor () <0x00010> at (wrapper runtime-invoke) object.runtime_invoke_void (object,intptr,intptr,intptr) <0xffffffff> at <0xffffffff> at NzbDrone.Mono.MonoRuntimeProvider..ctor (NzbDrone.Common.IServiceProvider,NLog.Logger) <0x00024> at (wrapper dynamic-method) object.lambda_method (System.Runtime.CompilerServices.Closure,object[]) <0x0012c> at TinyIoC.TinyIoCContainer.ConstructType (System.Type,System.Type,System.Reflection.ConstructorInfo,TinyIoC.NamedParameterOverloads,TinyIoC.ResolveOptions) <0x0053b> at TinyIoC.TinyIoCContainer.ConstructType (System.Type,System.Type,System.Reflection.ConstructorInfo,TinyIoC.ResolveOptions) <0x0004d> at TinyIoC.TinyIoCContainer/SingletonFactory.GetObject (System.Type,TinyIoC.TinyIoCContainer,TinyIoC.NamedParameterOverloads,TinyIoC.ResolveOptions) <0x0009b> at TinyIoC.TinyIoCContainer.ResolveInternal (TinyIoC.TinyIoCContainer/TypeRegistration,TinyIoC.NamedParameterOverloads,TinyIoC.ResolveOptions) <0x000be> at TinyIoC.TinyIoCContainer.Resolve (System.Type,string) <0x0007c> at NzbDrone.Common.Composition.Container/<>c__DisplayClass4.b__3 (TinyIoC.TinyIoCContainer,TinyIoC.NamedParameterOverloads) <0x00066> at TinyIoC.TinyIoCContainer/DelegateFactory.GetObject (System.Type,TinyIoC.TinyIoCContainer,TinyIoC.NamedParameterOverloads,TinyIoC.ResolveOptions) <0x00035> at TinyIoC.TinyIoCContainer.ResolveInternal (TinyIoC.TinyIoCContainer/TypeRegistration,TinyIoC.NamedParameterOverloads,TinyIoC.ResolveOptions) <0x000be> at TinyIoC.TinyIoCContainer.Resolve (System.Type) <0x0007f> at TinyIoC.TinyIoCContainer.Resolve () <0x00032> at NzbDrone.Common.Composition.Container.Resolve () <0x00041> at NzbDrone.Host.Bootstrap.GetApplicationMode (NzbDrone.Common.EnvironmentInfo.IStartupContext) <0x000c9> at NzbDrone.Host.Bootstrap.Start (NzbDrone.Common.EnvironmentInfo.StartupContext,NzbDrone.Host.IUserAlert,System.Action`1) <0x001c6> at NzbDrone.Console.ConsoleApp.Main (string[]) <0x000a2> at (wrapper runtime-invoke) .runtime_invoke_void_object (object,intptr,intptr,intptr) <0xffffffff> ================================================================= Got a SIGSEGV while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application. ================================================================= I confirmed this in Virtualbox by installing 10.2 with the same version of mono and sonarr listed, started sonarr successfully, then upgraded to 10.3, and was unable to start sonarr. I reported the issue on the sonarr forums, but to me, this seems more like an issue with mono on FreeBSD. From owner-freebsd-mono@freebsd.org Fri May 13 00:34:50 2016 Return-Path: Delivered-To: freebsd-mono@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 556E2B34CF5 for ; Fri, 13 May 2016 00:34:50 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: from mail-vk0-x22b.google.com (mail-vk0-x22b.google.com [IPv6:2607:f8b0:400c:c05::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 03EB21BFD for ; Fri, 13 May 2016 00:34:50 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: by mail-vk0-x22b.google.com with SMTP id s184so118599051vkb.3 for ; Thu, 12 May 2016 17:34:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=TMfWju24E5ji2EFwCglqqBB2fMpxDyzBR0p6VwD+8so=; b=id9BWg6A+pb6ZOa7hoT55tKSOpSOjBtAISugjR+3InOSrui/s+RdLX059EtgPaVreK eXdgSBlQ698hdN/FPr0iWvHauOcudi7hTtOVdOIKPd9uxVpuznbyyk5AIc9Kq7x2ovgY Wum5Y1rjAdfYef6f7hw3RKlaUSEKw3c6cwx6Iv1R3kyqPmtpgzEI8v4kSKdvrJCjPYul wYVAESQLiqiI//CTU8tSnVnYjdaZAytvA/e3yXh7muCI3Dn/1oCM2jfqIlNHB0M/dGlA 6XD8Aiz3VxMIOjNoIZitvsFHeItna38FjMiayyC7tvkRsa3/qQ+LSGKJIyrChOhJYmlL eJSg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=TMfWju24E5ji2EFwCglqqBB2fMpxDyzBR0p6VwD+8so=; b=Ez/ac6KrRP33/MDZ0Z9a1pHctqhzOv7G/3eq83CDIZAKkHtVhEDt1vNllWPceTSit2 xyXF9b59NRaqXeMMhUArInypceE36To/fn6h6Klto4PDHqa2R6ppnUp2Sf8XIrTYY5oN qVRWxcP3WmHih9Z56xLtFoqMbyrxDzHS926e9v3BnKZpRMcuINmwHUosFIpVKPErky+X vqp20qGUKsCgxunrDtqwEYv09ytrNQbBT6BHXny1usypJ9deHwGBh+iTG+mlwEGuvLn8 0LqeFw3jqtoQtjVr+31bj2hFYdW6J+8IiEJ7Js1ho32kN4TtZMFTLJAhDqk6tXZJTm1o rcLQ== X-Gm-Message-State: AOPr4FWP3bn9ii15k+BLs5wTveEOUaL1wxrIbrgQBMit8CltfW5omKRRDrWQHv6J5SlsJylj96eJEi55Qpopsg== MIME-Version: 1.0 X-Received: by 10.31.74.69 with SMTP id x66mr6189764vka.145.1463099688982; Thu, 12 May 2016 17:34:48 -0700 (PDT) Received: by 10.31.61.1 with HTTP; Thu, 12 May 2016 17:34:48 -0700 (PDT) In-Reply-To: References: Date: Thu, 12 May 2016 17:34:48 -0700 Message-ID: Subject: Re: Sonarr/Mono crash with SIGSEGV on 10.3-STABLE From: Russell Haley To: Mark Heppner Cc: Freebsd-mono Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-mono@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Mono and C# applications on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 May 2016 00:34:50 -0000 Okay, so reading the tea leaves: TinyIOC determines that the system is running against Mono and tries to load NzbDrone.Mono. The class NzbDrone.Mono.RuntimeProvider then blows up in the constructor. The file is here: https://github.com/Sonarr/Sonarr/blob/develop/src/NzbDrone.Mono/MonoRuntimeProvider.cs I see that it's doing something with an NLog logger. (_logger = logger). SO the issue could be: - Something to do with the call to base(serviceProvider, logger) ? - A filewatcher issue? I know there has been/are issues with using the native file watcher component (uses kqueues). In a custom build of MonoDevelop I had to turn off native file watcher and use the "Managed File Watcher". Perhaps in the base constructor NLog is doing something with filewatchers? I have also seen Monodevelop try and copy files from /tmp to another directory. If you are using PC-BSD or (FreeBSD with ZFS), then it blows up because the native "move" doesn't work across different filesystems. I had to write a custom function that caught the exception and then performed an actual copy, then delete style move (yuck!). Upon inspecting the FreeBSD 10.3-RELEASE notes I see that there was a small change made to kqueues, but it doesn't seem significant. I also noted that you stated you were using 10.3-STABLE which is technically still a development branch. Perhaps reviewing the release notes may give you some insight? https://www.freebsd.org/releases/10.3R/relnotes.html My money is on a filewatcher as the culprit. HTH Russ On Thu, May 12, 2016 at 9:15 AM, Mark Heppner wrote: > I was able to run sonarr-2.0.0.3953 on mono-4.2.3.4 on 10.2-STABLE. After > upgrading to 10.3-STABLE, the program now crashes with this stacktrace: > > > > [Info] Bootstrap: Starting Sonarr - /usr/local/share/sonarr/NzbDrone.exe - > Version 2.0.0.3953 > [Info] AppFolderInfo: Data directory is being overridden to > [/usr/local/sonarr] > Stacktrace: > > at <0xffffffff> > at (wrapper managed-to-native) > System.Diagnostics.Process.ProcessName_internal (intptr) <0xffffffff> > at System.Diagnostics.Process.get_ProcessName () <0x00047> > at (wrapper remoting-invoke-with-check) > System.Diagnostics.Process.get_ProcessName () <0xffffffff> > at NzbDrone.Common.EnvironmentInfo.RuntimeInfoBase.InternalIsProduction > () <0x00080> > at NzbDrone.Common.EnvironmentInfo.RuntimeInfoBase..cctor () <0x00010> > at (wrapper runtime-invoke) object.runtime_invoke_void > (object,intptr,intptr,intptr) <0xffffffff> > at <0xffffffff> > at NzbDrone.Mono.MonoRuntimeProvider..ctor > (NzbDrone.Common.IServiceProvider,NLog.Logger) <0x00024> > at (wrapper dynamic-method) object.lambda_method > (System.Runtime.CompilerServices.Closure,object[]) <0x0012c> > at TinyIoC.TinyIoCContainer.ConstructType > (System.Type,System.Type,System.Reflection.ConstructorInfo,TinyIoC.NamedParameterOverloads,TinyIoC.ResolveOptions) > <0x0053b> > at TinyIoC.TinyIoCContainer.ConstructType > (System.Type,System.Type,System.Reflection.ConstructorInfo,TinyIoC.ResolveOptions) > <0x0004d> > at TinyIoC.TinyIoCContainer/SingletonFactory.GetObject > (System.Type,TinyIoC.TinyIoCContainer,TinyIoC.NamedParameterOverloads,TinyIoC.ResolveOptions) > <0x0009b> > at TinyIoC.TinyIoCContainer.ResolveInternal > (TinyIoC.TinyIoCContainer/TypeRegistration,TinyIoC.NamedParameterOverloads,TinyIoC.ResolveOptions) > <0x000be> > at TinyIoC.TinyIoCContainer.Resolve (System.Type,string) <0x0007c> > at > NzbDrone.Common.Composition.Container/<>c__DisplayClass4.b__3 > (TinyIoC.TinyIoCContainer,TinyIoC.NamedParameterOverloads) <0x00066> > at TinyIoC.TinyIoCContainer/DelegateFactory.GetObject > (System.Type,TinyIoC.TinyIoCContainer,TinyIoC.NamedParameterOverloads,TinyIoC.ResolveOptions) > <0x00035> > at TinyIoC.TinyIoCContainer.ResolveInternal > (TinyIoC.TinyIoCContainer/TypeRegistration,TinyIoC.NamedParameterOverloads,TinyIoC.ResolveOptions) > <0x000be> > at TinyIoC.TinyIoCContainer.Resolve (System.Type) <0x0007f> > at TinyIoC.TinyIoCContainer.Resolve () <0x00032> > at NzbDrone.Common.Composition.Container.Resolve () <0x00041> > at NzbDrone.Host.Bootstrap.GetApplicationMode > (NzbDrone.Common.EnvironmentInfo.IStartupContext) <0x000c9> > at NzbDrone.Host.Bootstrap.Start > (NzbDrone.Common.EnvironmentInfo.StartupContext,NzbDrone.Host.IUserAlert,System.Action`1) > <0x001c6> > at NzbDrone.Console.ConsoleApp.Main (string[]) <0x000a2> > at (wrapper runtime-invoke) .runtime_invoke_void_object > (object,intptr,intptr,intptr) <0xffffffff> > > ================================================================= > Got a SIGSEGV while executing native code. This usually indicates > a fatal error in the mono runtime or one of the native libraries > used by your application. > ================================================================= > > > > I confirmed this in Virtualbox by installing 10.2 with the same version of > mono and sonarr listed, started sonarr successfully, then upgraded to 10.3, > and was unable to start sonarr. I reported the issue on the sonarr forums, > but to me, this seems more like an issue with mono on FreeBSD. > _______________________________________________ > freebsd-mono@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-mono > To unsubscribe, send any mail to "freebsd-mono-unsubscribe@freebsd.org" From owner-freebsd-mono@freebsd.org Fri May 13 14:22:20 2016 Return-Path: Delivered-To: freebsd-mono@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9F914B3A946 for ; Fri, 13 May 2016 14:22:20 +0000 (UTC) (envelope-from rsmith4204200@gmail.com) Received: from mail-wm0-x22b.google.com (mail-wm0-x22b.google.com [IPv6:2a00:1450:400c:c09::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2BBEA1B86 for ; Fri, 13 May 2016 14:22:20 +0000 (UTC) (envelope-from rsmith4204200@gmail.com) Received: by mail-wm0-x22b.google.com with SMTP id a17so33008342wme.0 for ; Fri, 13 May 2016 07:22:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=SI45M9mehVV68hF50boL/6AgDMypzeWL4//T9TbXE/c=; b=gJgWcXQBsKkavakleDy635eSaqkDjGE3W2bYMX6hNPgm532sQ80J1RY7pCrE1ezMVn XeVjhSvvHREDXZdOBuaClLIbbzYPJQCkQIvZ0b3ty//lJKvNFtfLdZ+gKVhxVRTykJZz BD+usVJqMJsFpeYpRHgT2wLDM3/edNcRFmJPvbgD3Ns+wufgXgyQhbCYGJlzPU/3+T8B hkp+wmE5G+0obqwcOUZh9H2ucivxNrlkcgB4+Egfq6fyUNUMXLg1I22Jbncpe8+VrIBC AEJVEx9LrGeelxZ2+tBD1JTMmfADgfgtGvwhQkqmENRujPhSWzU7B9+JWawsm6LpND8H ZOIA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=SI45M9mehVV68hF50boL/6AgDMypzeWL4//T9TbXE/c=; b=g01ahpjd8BeePILayAZL7wtscfS5D10idwmjhxOjy5S5ycF2syQ2Y6io2FVKqb0m1e 5rEIxNeDaPqLg/Kd+yRAgxz+JUcJkeFQcNCiXMmser9mTRa5eEd9/YcIIWW/u8XbpWfW 9eXE/F3aJKQamgza33Lg3lQL1L9MpF6PMXGxF6dcnSXhu/r78mBFCx1L8t/VQacE2c7V ++AiNMVrwtuYjB6z44NecZapR/ib1UHlzCUU5pwOVvtMQw1ZxAgPMMVZ4aQuj5pQ1RAz oGcKWF9Flb4no0o+72Qq6dc8m82jpnlwaqUTl92xll0IG0a+gpKtG7VahGug6Xv6BOn7 eohw== X-Gm-Message-State: AOPr4FWK330q/ZckjE0pecZgk/K8Kc8aq+6rHZ2txSqYLxkgmLaVxBxXOYXgQ6hbOwdKtf2MJf9+7gS6kbEbHA== MIME-Version: 1.0 X-Received: by 10.194.104.138 with SMTP id ge10mr15356689wjb.85.1463149338700; Fri, 13 May 2016 07:22:18 -0700 (PDT) Received: by 10.28.167.203 with HTTP; Fri, 13 May 2016 07:22:18 -0700 (PDT) In-Reply-To: References: Date: Fri, 13 May 2016 10:22:18 -0400 Message-ID: Subject: Re: Sonarr/Mono crash with SIGSEGV on 10.3-STABLE From: Randy Smith To: Russell Haley Cc: Freebsd-mono Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-mono@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Mono and C# applications on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 May 2016 14:22:20 -0000 I just checked with a copy of 10.3-RELEASE and it works fine. The version of 10.3-STABLE I'm on is r298222 (April 18), so I guess I can at least narrow it down between those two revisions of 10.3. From what I can tell, 10.3-RELEASE was copied from stable/10@296371, correct? How can I further narrow down which revision the problem started at? Should I just try different versions of the stable branch until I find where it happens? If it helps, I've been testing this with FreeBSD, using ZFS. On Thu, May 12, 2016 at 8:34 PM, Russell Haley wrote: > Okay, so reading the tea leaves: > > TinyIOC determines that the system is running against Mono and tries > to load NzbDrone.Mono. The class NzbDrone.Mono.RuntimeProvider then > blows up in the constructor. The file is here: > > > https://github.com/Sonarr/Sonarr/blob/develop/src/NzbDrone.Mono/MonoRuntimeProvider.cs > > I see that it's doing something with an NLog logger. (_logger = logger). > > SO the issue could be: > - Something to do with the call to base(serviceProvider, logger) ? > - A filewatcher issue? I know there has been/are issues with using the > native file watcher component (uses kqueues). In a custom build of > MonoDevelop I had to turn off native file watcher and use the "Managed > File Watcher". Perhaps in the base constructor NLog is doing something > with filewatchers? > > I have also seen Monodevelop try and copy files from /tmp to another > directory. If you are using PC-BSD or (FreeBSD with ZFS), then it > blows up because the native "move" doesn't work across different > filesystems. I had to write a custom function that caught the > exception and then performed an actual copy, then delete style move > (yuck!). > > Upon inspecting the FreeBSD 10.3-RELEASE notes I see that there was a > small change made to kqueues, but it doesn't seem significant. I also > noted that you stated you were using 10.3-STABLE which is technically > still a development branch. Perhaps reviewing the release notes may > give you some insight? > https://www.freebsd.org/releases/10.3R/relnotes.html > > My money is on a filewatcher as the culprit. > > HTH > Russ > > On Thu, May 12, 2016 at 9:15 AM, Mark Heppner > wrote: > > I was able to run sonarr-2.0.0.3953 on mono-4.2.3.4 on 10.2-STABLE. After > > upgrading to 10.3-STABLE, the program now crashes with this stacktrace: > > > > > > > > [Info] Bootstrap: Starting Sonarr - /usr/local/share/sonarr/NzbDrone.exe > - > > Version 2.0.0.3953 > > [Info] AppFolderInfo: Data directory is being overridden to > > [/usr/local/sonarr] > > Stacktrace: > > > > at <0xffffffff> > > at (wrapper managed-to-native) > > System.Diagnostics.Process.ProcessName_internal (intptr) <0xffffffff> > > at System.Diagnostics.Process.get_ProcessName () <0x00047> > > at (wrapper remoting-invoke-with-check) > > System.Diagnostics.Process.get_ProcessName () <0xffffffff> > > at NzbDrone.Common.EnvironmentInfo.RuntimeInfoBase.InternalIsProduction > > () <0x00080> > > at NzbDrone.Common.EnvironmentInfo.RuntimeInfoBase..cctor () <0x00010> > > at (wrapper runtime-invoke) object.runtime_invoke_void > > (object,intptr,intptr,intptr) <0xffffffff> > > at <0xffffffff> > > at NzbDrone.Mono.MonoRuntimeProvider..ctor > > (NzbDrone.Common.IServiceProvider,NLog.Logger) <0x00024> > > at (wrapper dynamic-method) object.lambda_method > > (System.Runtime.CompilerServices.Closure,object[]) <0x0012c> > > at TinyIoC.TinyIoCContainer.ConstructType > > > (System.Type,System.Type,System.Reflection.ConstructorInfo,TinyIoC.NamedParameterOverloads,TinyIoC.ResolveOptions) > > <0x0053b> > > at TinyIoC.TinyIoCContainer.ConstructType > > > (System.Type,System.Type,System.Reflection.ConstructorInfo,TinyIoC.ResolveOptions) > > <0x0004d> > > at TinyIoC.TinyIoCContainer/SingletonFactory.GetObject > > > (System.Type,TinyIoC.TinyIoCContainer,TinyIoC.NamedParameterOverloads,TinyIoC.ResolveOptions) > > <0x0009b> > > at TinyIoC.TinyIoCContainer.ResolveInternal > > > (TinyIoC.TinyIoCContainer/TypeRegistration,TinyIoC.NamedParameterOverloads,TinyIoC.ResolveOptions) > > <0x000be> > > at TinyIoC.TinyIoCContainer.Resolve (System.Type,string) <0x0007c> > > at > > > NzbDrone.Common.Composition.Container/<>c__DisplayClass4.b__3 > > (TinyIoC.TinyIoCContainer,TinyIoC.NamedParameterOverloads) <0x00066> > > at TinyIoC.TinyIoCContainer/DelegateFactory.GetObject > > > (System.Type,TinyIoC.TinyIoCContainer,TinyIoC.NamedParameterOverloads,TinyIoC.ResolveOptions) > > <0x00035> > > at TinyIoC.TinyIoCContainer.ResolveInternal > > > (TinyIoC.TinyIoCContainer/TypeRegistration,TinyIoC.NamedParameterOverloads,TinyIoC.ResolveOptions) > > <0x000be> > > at TinyIoC.TinyIoCContainer.Resolve (System.Type) <0x0007f> > > at TinyIoC.TinyIoCContainer.Resolve () <0x00032> > > at NzbDrone.Common.Composition.Container.Resolve () <0x00041> > > at NzbDrone.Host.Bootstrap.GetApplicationMode > > (NzbDrone.Common.EnvironmentInfo.IStartupContext) <0x000c9> > > at NzbDrone.Host.Bootstrap.Start > > > (NzbDrone.Common.EnvironmentInfo.StartupContext,NzbDrone.Host.IUserAlert,System.Action`1) > > <0x001c6> > > at NzbDrone.Console.ConsoleApp.Main (string[]) <0x000a2> > > at (wrapper runtime-invoke) .runtime_invoke_void_object > > (object,intptr,intptr,intptr) <0xffffffff> > > > > ================================================================= > > Got a SIGSEGV while executing native code. This usually indicates > > a fatal error in the mono runtime or one of the native libraries > > used by your application. > > ================================================================= > > > > > > > > I confirmed this in Virtualbox by installing 10.2 with the same version > of > > mono and sonarr listed, started sonarr successfully, then upgraded to > 10.3, > > and was unable to start sonarr. I reported the issue on the sonarr > forums, > > but to me, this seems more like an issue with mono on FreeBSD. > > _______________________________________________ > > freebsd-mono@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-mono > > To unsubscribe, send any mail to "freebsd-mono-unsubscribe@freebsd.org" > From owner-freebsd-mono@freebsd.org Fri May 13 15:57:57 2016 Return-Path: Delivered-To: freebsd-mono@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6D339B3A1C0 for ; Fri, 13 May 2016 15:57:57 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: from mail-pf0-x22c.google.com (mail-pf0-x22c.google.com [IPv6:2607:f8b0:400e:c00::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3DF1D166C for ; Fri, 13 May 2016 15:57:57 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: by mail-pf0-x22c.google.com with SMTP id c189so45279098pfb.3 for ; Fri, 13 May 2016 08:57:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:content-transfer-encoding:message-id:date:subject:from :in-reply-to:references:to:cc; bh=vrpN9v64h3yjEh9/jtD6i4yp9mhkVo+PZlfTYwszyTk=; b=Kmgo12j+ISHoc4KyyNYK27PcS+6OKsXmhcZmvQeNXcp3pwrF9E73e5VwjNM0Sy98C5 3Dt9dh9P6IDM+pOX9poAUE9ckuaVdCamdwxqld/sZQyTH7y9pZIy/cxNb6eBhW2xByue 8Sa9xTl0p5B8zu2v3HPJUV+Mr4WiUyCH4vwFyuyqqqe1nL08XEfH79vS1XwoNd6+RJeY qofxFVBR/tNrc8m9HKF+upfLgbkeMQWgtkS6owgPNfSh51aoyOOJxMUgzv1evyLGl9oG QKFIk2JkKz0R+1FrFYBKQNmoViXzMCbaR/dl3UdYMCNOSkQpO2TZj6jZePi3K0BkP29A LRDg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:content-transfer-encoding :message-id:date:subject:from:in-reply-to:references:to:cc; bh=vrpN9v64h3yjEh9/jtD6i4yp9mhkVo+PZlfTYwszyTk=; b=DumH55DKzqIraPYwZTslo5E5z0DhwQIF9RfvWcOWCNdY4XK+9JLWWGrN/Y6CXlkUSL 2MpSNIaJ+2PMbY2vAWj28zUGMtBpR0C3BBve4I7ayACita/a062kyLzFp8jIhg47fEFd Jm6GKmHX4eUlYv15Jt2neMXFJYc5bfp+e1t3BwTw91Fa0rdFBIAFFp5GKGwaWUDC7QFa oy7bfkfaUoQ3bsGoDzvBWOMlMnFBC/LqQDa6RpdozYQKcty8HwhJ5/VhIElGBD/gWZe4 MYOdgk2St+l9v4qPaJXEUg/7DY7mak/iNPB3XKmsgYkb36CjBWOYMUVCPCPi6g/UyIyY Zijg== X-Gm-Message-State: AOPr4FUzwRaMq0Xx8z5bclxpFm+ZfGnhH0ikHKudk9Pt05I7BWLvuZw9/BblmheE4WPAlw== X-Received: by 10.98.27.129 with SMTP id b123mr24281643pfb.111.1463155076674; Fri, 13 May 2016 08:57:56 -0700 (PDT) Received: from [127.0.0.1] ([209.52.88.3]) by smtp.gmail.com with ESMTPSA id lq10sm28451400pab.36.2016.05.13.08.57.55 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 13 May 2016 08:57:56 -0700 (PDT) X-Mailer: BlackBerry Email (10.3.2.2876) Message-ID: <20160513155754.4534354.1362.6201@gmail.com> Date: Fri, 13 May 2016 08:57:54 -0700 Subject: Re: Sonarr/Mono crash with SIGSEGV on 10.3-STABLE From: Russell Haley In-Reply-To: References: To: Randy Smith Cc: Freebsd-mono MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-mono@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Mono and C# applications on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 May 2016 15:57:57 -0000 From owner-freebsd-mono@freebsd.org Fri May 13 19:32:55 2016 Return-Path: Delivered-To: freebsd-mono@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B945FB3A454 for ; Fri, 13 May 2016 19:32:55 +0000 (UTC) (envelope-from bounce+8cc18d.d053-freebsd-mono=freebsd.org@markheppner.com) Received: from mail-s91.mailgun.info (mail-s91.mailgun.info [184.173.153.219]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7A5A51E98 for ; Fri, 13 May 2016 19:32:54 +0000 (UTC) (envelope-from bounce+8cc18d.d053-freebsd-mono=freebsd.org@markheppner.com) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=markheppner.com; q=dns/txt; s=krs; t=1463167968; h=Content-Type: Cc: To: Subject: Message-ID: Date: From: References: In-Reply-To: MIME-Version: Sender; bh=L/K+VerEm8mrjMmQXC9OgeC9T4CmIBtwkl8v7Z03H34=; b=oBQtpBKu3sfITejMvtBuE70Pg6+RmcaiISWthrZt8mjr6gyI6upNxAY2P7OaD/kmyRZKBXEa ef52hrIUUHiItg0uz8IUrKjA5OAQi4TySaC3o8sSIajLgyj3EdpeNEli2B04u2gwwhb2ECAD lgkh6WtBmCA4+s6lmo8ykxqb1LA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=markheppner.com; s=krs; q=dns; h=Sender: MIME-Version: In-Reply-To: References: From: Date: Message-ID: Subject: To: Cc: Content-Type; b=K1tCRXtHLVf8+y3vm/BjFJaqlUPYhytCZZ4sHonFvhTlB3tD3rPD7YL3wlJPKkvSAQcyqI hfmtx31GNRsGU5Geu9JkN+gl5RE5n2krTz1GHxp529Oj+6PlGEhGrGkaXi1+5iuSaaLtoolZ hCrkyVRUHK2+dSjnOhPHg6uBmlhio= Sender: freebsd@markheppner.com X-Mailgun-Sid: WyJhNGEyOSIsICJmcmVlYnNkLW1vbm9AZnJlZWJzZC5vcmciLCAiZDA1MyJd Received: from mail-wm0-f43.google.com (mail-wm0-f43.google.com [74.125.82.43]) by mxa.mailgun.org with ESMTP id 57362bde.7f83554e70f0-in02; Fri, 13 May 2016 19:32:46 -0000 (UTC) Received: by mail-wm0-f43.google.com with SMTP id g17so45561987wme.1 for ; Fri, 13 May 2016 12:32:46 -0700 (PDT) X-Gm-Message-State: AOPr4FVrEUSzZTNbDqlpJ2ftn2G6/ABXgF3kLa230zV2opz31XftwyOxhRbOjUw+IvNtJLnPZLTVsJ6/FWkEGg== X-Received: by 10.194.223.41 with SMTP id qr9mr17226712wjc.61.1463167965374; Fri, 13 May 2016 12:32:45 -0700 (PDT) MIME-Version: 1.0 Received: by 10.28.167.203 with HTTP; Fri, 13 May 2016 12:32:05 -0700 (PDT) In-Reply-To: <20160513155754.4534354.1362.6201@gmail.com> References: <20160513155754.4534354.1362.6201@gmail.com> From: Mark Heppner Date: Fri, 13 May 2016 15:32:05 -0400 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Sonarr/Mono crash with SIGSEGV on 10.3-STABLE To: Russell Haley Cc: Freebsd-mono Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-mono@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Mono and C# applications on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 May 2016 19:32:55 -0000 It looks like it happens between revisions 296500 and 297000. That's probably as far as I can narrow it down to since building takes awhile. I'm not sure where to go from this point. Do you know if it's safe to downgrade from the revision I'm at on -STABLE to the -RELEASE version? Thanks for your help, this was my first time using the mailing lists! On Fri, May 13, 2016 at 11:57 AM, Russell Haley wrote: > This is just of the top of my head, but if you are really keen to find th= e > issue, you can query svn for which files have changed between revisions. > =E2=80=8ENarrow it down and then start diffing files. Author commit notes= will help > too. I don't know svn commands by heart yet. > > I know you didn't ask for it but: this issue is just a bug in my opinion. > If you are really looking for stability tests to run, build 11-CURRENT an= d > test=E2=80=8E. :D > > Cheers > Russ > > Sent from my BlackBerry 10 smartphone on the Koodo network. > *From: *Randy Smith > *Sent: *Friday, May 13, 2016 7:22 AM > *To: *Russell Haley > *Cc: *Freebsd-mono > *Subject: *Re: Sonarr/Mono crash with SIGSEGV on 10.3-STABLE > > I just checked with a copy of 10.3-RELEASE and it works fine. The version > of 10.3-STABLE I'm on is r298222 (April 18), so I guess I can at least > narrow it down between those two revisions of 10.3. From what I can tell, > 10.3-RELEASE was copied from stable/10@296371, correct? How can I further > narrow down which revision the problem started at? Should I just try > different versions of the stable branch until I find where it happens? If > it helps, I've been testing this with FreeBSD, using ZFS. > > On Thu, May 12, 2016 at 8:34 PM, Russell Haley > wrote: > >> Okay, so reading the tea leaves: >> >> TinyIOC determines that the system is running against Mono and tries >> to load NzbDrone.Mono. The class NzbDrone.Mono.RuntimeProvider then >> blows up in the constructor. The file is here: >> >> >> https://github.com/Sonarr/Sonarr/blob/develop/src/NzbDrone.Mono/MonoRunt= imeProvider.cs >> >> I see that it's doing something with an NLog logger. (_logger =3D logger= ). >> >> SO the issue could be: >> - Something to do with the call to base(serviceProvider, logger) ? >> - A filewatcher issue? I know there has been/are issues with using the >> native file watcher component (uses kqueues). In a custom build of >> MonoDevelop I had to turn off native file watcher and use the "Managed >> File Watcher". Perhaps in the base constructor NLog is doing something >> with filewatchers? >> >> I have also seen Monodevelop try and copy files from /tmp to another >> directory. If you are using PC-BSD or (FreeBSD with ZFS), then it >> blows up because the native "move" doesn't work across different >> filesystems. I had to write a custom function that caught the >> exception and then performed an actual copy, then delete style move >> (yuck!). >> >> Upon inspecting the FreeBSD 10.3-RELEASE notes I see that there was a >> small change made to kqueues, but it doesn't seem significant. I also >> noted that you stated you were using 10.3-STABLE which is technically >> still a development branch. Perhaps reviewing the release notes may >> give you some insight? >> https://www.freebsd.org/releases/10.3R/relnotes.html >> >> My money is on a filewatcher as the culprit. >> >> HTH >> Russ >> >> On Thu, May 12, 2016 at 9:15 AM, Mark Heppner >> wrote: >> > I was able to run sonarr-2.0.0.3953 on mono-4.2.3.4 on 10.2-STABLE. >> After >> > upgrading to 10.3-STABLE, the program now crashes with this stacktrace= : >> > >> > >> > >> > [Info] Bootstrap: Starting Sonarr - >> /usr/local/share/sonarr/NzbDrone.exe - >> > Version 2.0.0.3953 >> > [Info] AppFolderInfo: Data directory is being overridden to >> > [/usr/local/sonarr] >> > Stacktrace: >> > >> > at <0xffffffff> >> > at (wrapper managed-to-native) >> > System.Diagnostics.Process.ProcessName_internal (intptr) <0xffffffff> >> > at System.Diagnostics.Process.get_ProcessName () <0x00047> >> > at (wrapper remoting-invoke-with-check) >> > System.Diagnostics.Process.get_ProcessName () <0xffffffff> >> > at >> NzbDrone.Common.EnvironmentInfo.RuntimeInfoBase.InternalIsProduction >> > () <0x00080> >> > at NzbDrone.Common.EnvironmentInfo.RuntimeInfoBase..cctor () <0x0001= 0> >> > at (wrapper runtime-invoke) object.runtime_invoke_void >> > (object,intptr,intptr,intptr) <0xffffffff> >> > at <0xffffffff> >> > at NzbDrone.Mono.MonoRuntimeProvider..ctor >> > (NzbDrone.Common.IServiceProvider,NLog.Logger) <0x00024> >> > at (wrapper dynamic-method) object.lambda_method >> > (System.Runtime.CompilerServices.Closure,object[]) <0x0012c> >> > at TinyIoC.TinyIoCContainer.ConstructType >> > >> (System.Type,System.Type,System.Reflection.ConstructorInfo,TinyIoC.Named= ParameterOverloads,TinyIoC.ResolveOptions) >> > <0x0053b> >> > at TinyIoC.TinyIoCContainer.ConstructType >> > >> (System.Type,System.Type,System.Reflection.ConstructorInfo,TinyIoC.Resol= veOptions) >> > <0x0004d> >> > at TinyIoC.TinyIoCContainer/SingletonFactory.GetObject >> > >> (System.Type,TinyIoC.TinyIoCContainer,TinyIoC.NamedParameterOverloads,Ti= nyIoC.ResolveOptions) >> > <0x0009b> >> > at TinyIoC.TinyIoCContainer.ResolveInternal >> > >> (TinyIoC.TinyIoCContainer/TypeRegistration,TinyIoC.NamedParameterOverloa= ds,TinyIoC.ResolveOptions) >> > <0x000be> >> > at TinyIoC.TinyIoCContainer.Resolve (System.Type,string) <0x0007c> >> > at >> > >> NzbDrone.Common.Composition.Container/<>c__DisplayClass4.b__3 >> > (TinyIoC.TinyIoCContainer,TinyIoC.NamedParameterOverloads) <0x00066> >> > at TinyIoC.TinyIoCContainer/DelegateFactory.GetObject >> > >> (System.Type,TinyIoC.TinyIoCContainer,TinyIoC.NamedParameterOverloads,Ti= nyIoC.ResolveOptions) >> > <0x00035> >> > at TinyIoC.TinyIoCContainer.ResolveInternal >> > >> (TinyIoC.TinyIoCContainer/TypeRegistration,TinyIoC.NamedParameterOverloa= ds,TinyIoC.ResolveOptions) >> > <0x000be> >> > at TinyIoC.TinyIoCContainer.Resolve (System.Type) <0x0007f> >> > at TinyIoC.TinyIoCContainer.Resolve () <0x00032> >> > at NzbDrone.Common.Composition.Container.Resolve () <0x00041> >> > at NzbDrone.Host.Bootstrap.GetApplicationMode >> > (NzbDrone.Common.EnvironmentInfo.IStartupContext) <0x000c9> >> > at NzbDrone.Host.Bootstrap.Start >> > >> (NzbDrone.Common.EnvironmentInfo.StartupContext,NzbDrone.Host.IUserAlert= ,System.Action`1) >> > <0x001c6> >> > at NzbDrone.Console.ConsoleApp.Main (string[]) <0x000a2> >> > at (wrapper runtime-invoke) .runtime_invoke_void_object >> > (object,intptr,intptr,intptr) <0xffffffff> >> > >> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> > Got a SIGSEGV while executing native code. This usually indicates >> > a fatal error in the mono runtime or one of the native libraries >> > used by your application. >> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> > >> > >> > >> > I confirmed this in Virtualbox by installing 10.2 with the same versio= n >> of >> > mono and sonarr listed, started sonarr successfully, then upgraded to >> 10.3, >> > and was unable to start sonarr. I reported the issue on the sonarr >> forums, >> > but to me, this seems more like an issue with mono on FreeBSD. >> > _______________________________________________ >> > freebsd-mono@freebsd.org mailing list >> > https://lists.freebsd.org/mailman/listinfo/freebsd-mono >> > To unsubscribe, send any mail to "freebsd-mono-unsubscribe@freebsd.org= " >> > > > From owner-freebsd-mono@freebsd.org Fri May 13 19:51:56 2016 Return-Path: Delivered-To: freebsd-mono@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0BD43B3A9EC for ; Fri, 13 May 2016 19:51:56 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: from mail-pf0-x22c.google.com (mail-pf0-x22c.google.com [IPv6:2607:f8b0:400e:c00::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CFF561C18 for ; Fri, 13 May 2016 19:51:55 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: by mail-pf0-x22c.google.com with SMTP id c189so47084150pfb.3 for ; Fri, 13 May 2016 12:51:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:content-transfer-encoding:message-id:date:subject:from :in-reply-to:references:to:cc; bh=T1TW0+BI/bNVTxrgo4SLM3q7TivSNPcwe2O7wgDFwJI=; b=TWtXdv8g8yYLyAWUBw8rzC/So4mrubnIM43DKodrYdGDUVa4wo/eg+GfdrMcvfowQY 05CLiprUzTB2GeuB2OiRoevub68/Wnq3/5axl6kBjRGIDkLj/fzKuZUZGsro4nWuiMJl mT1gbjYgfL1b6K/XPUsaJD5ReXXyHkzu1O+dgsMm/BalUp5sN4XMP1reqAWqDspLP7do iVRkoPW/cbjgOGlpoe56m3hIaphwdLQNP6JzpVbsz8QGoafoBHuKvvMmv34sUhUCuHTN Xb7TO+dLL0Z+dMqlUF77dSPCSy6u3+kKLrtQcYLYAasvxfSYRm/gUmk200q2gmt4DWHE 3DUQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:content-transfer-encoding :message-id:date:subject:from:in-reply-to:references:to:cc; bh=T1TW0+BI/bNVTxrgo4SLM3q7TivSNPcwe2O7wgDFwJI=; b=Seqh2/+RvD1e+UWGDNUqQxLoGyXz9LzO3Xg3dMX10tLwBH4/3jKDXaMer2xSTOaijt snQ7IuOa5nz/+9LxJ9INuzGtyhzJmDsM9dlfyZ1p/jpT6sDElk8UyUkhOmlSOIEb/jGB Hp+7DNOa1enDjHQ5h3Q496dPItLTxdtc1WLzz8Jl6RwW05Mj/qN4RX0C5pEGhsmnk86r 3lAVwAxTqDugtfiscIsN0boGV2VSkXZbtzhs8er72vKPOaEqNnXBm1WIaDy3IfjycW26 LnfmkNEWfFrXoiZxAiPKZQTTQgngUPTktgK0izi9ANSGTB4DjL2CO1Mqj+R6ajZ6NlYw zp5A== X-Gm-Message-State: AOPr4FUbDYnYUR1nBj7wq1DBf77p5rQEOZf8cuG4cD38JB2iPTPpYK6Eox3xf7j5xAk3hw== X-Received: by 10.98.95.4 with SMTP id t4mr25943793pfb.162.1463169115383; Fri, 13 May 2016 12:51:55 -0700 (PDT) Received: from [127.0.0.1] ([209.52.88.3]) by smtp.gmail.com with ESMTPSA id lz5sm29332477pab.34.2016.05.13.12.51.52 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 13 May 2016 12:51:54 -0700 (PDT) X-Mailer: BlackBerry Email (10.3.2.2876) Message-ID: <20160513195152.4534354.68373.6212@gmail.com> Date: Fri, 13 May 2016 12:51:52 -0700 Subject: Re: Sonarr/Mono crash with SIGSEGV on 10.3-STABLE From: Russell Haley In-Reply-To: References: <20160513155754.4534354.1362.6201@gmail.com> To: Mark Heppner Cc: Freebsd-mono MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-mono@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Mono and C# applications on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 May 2016 19:51:56 -0000