Closed ksjoberg closed 5 years ago
Possibly related are that we are dependent on a assembly binding redirect for MySql.Web.dll to find its references as MySql.Data.dll are of a different version than the referenced version:
Hey @kjosberg, thanks for the report! Would you be willing to deploy with nuget 1.1 and msi 1.1 to see if you get the same behavior? We made some fairly substantial changes on version restrictions for 1.2 and this would be helpful for narrowing down our trouble shooting.
Unfortunately version 1.1.0 of the Nuget package does not install into our .csproj-based project.
Let’s be clear: first time we saw this was when the app was upgraded to 1.2 but the profiler dll was still at 1.1.
I have managed to reproduce this locally, with an exception being thrown at clr!AssemblySpec::InitializeSpec+0x42
but only on application recycles (meaning for instance, a reload after a web.config change).
I'm still seeing this issue even with 1.6.0.
@ksjoberg: This is high priority issue and we are actively working on it. Sorry about the lack of updates on this thread.
@ksjoberg Would you be able to provide the binding redirect and the actual version of your mysql assemblies for our testing?
MySql.Web.dll 6.3.7.0 MySql.Data.dll 6.10.8.0
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="MySql.Data" publicKeyToken="c5687fc88969c44d" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-6.10.8.0" newVersion="6.10.8.0" />
</dependentAssembly>
</assemblyBinding>
Any progress of this issue?
Hi @ksjoberg,
I put a request for the dump files in the other ticket, https://github.com/DataDog/dd-trace-dotnet/issues/541, but it is for this ticket that I meant to ask for them. Thanks
Hi @bobuva,
I added it to the internal Zendesk ticket #225652.
Thanks @ksjoberg -- I'll get back to you after looking at it.
@ksjoberg Based on the feedback we got from you in the Datadog support ticket, this crash appears to be fixed for you with 1.9.0. If you could confirm here before I close this ticket? Thanks!
Can't reproduce this more; 1.8.0 had the #541 issue, and 1.9.0 seems to work fine.
Describe the bug We're experiencing an issue where our application pool crashes, primarily when we make new deploys. We observe the following events in the Event Viewer:
and
To Reproduce We don't have a consistent repro of this, but when it happens for us is when we deploy a new set of DLLs into an already running application pool with our deployment tool (Octopus Deploy)
Expected behavior We expect the W3WP to continue running, which allows any existing keepalives to continue living and be served by the updated application.
Runtime environment:
From what we observed: MSI 1.1.0, Nuget 1.0.0 doesn't crash. MSI 1.1.0, Nuget 1.2.0 crashes, as well does MSI 1.2.0 and Nuget 1.2.0.
Additional context We've gathered two memory dumps, one in each crashing setup. If it crashes, it has crashed while JITting
MySql.Web.Common.SchemaManager.GetSchemaVersion(System.String)
The stack trace below is quite noisy and potentially confusing because it is "scraped". A line to highlight is
0000008e09f3aae0 00007ffcdc1d9fb5 clr!AssemblySpec::InitializeSpec+0x42 ====> Exception cxr@0000008e09f39d00
which triggers the application's termination.Are any symbols available for the native profiling assembly so that the symbols can be resolved better?