Closed s-tokutake closed 4 years ago
Hi @s-tokutake, is this new to 1.6.1 or did this happen in 1.6.0 as well?
Is there anything about the nested web forms App4
that is particularly different from the others?
Does it have specific security settings?
@colin-higgins thanks for your reply.
is this new to 1.6.1 or did this happen in 1.6.0 as well?
Does it have specific security settings?
@s-tokutake Do you know if any of the web applications are consuming the Nuget package (https://www.nuget.org/packages/Datadog.Trace.ClrProfiler.Managed/)? If they are, would you mind listing the versions for each app? In fact, if you wouldn't mind sharing the dependencies & versions for each application, that could greatly help us troubleshoot this issue. Thank you.
Do you know if any of the web applications are consuming the Nuget package )?
No. These apps don't use Datadog.Trace.ClrProfiler.Managed
.
Would like to chime in and note that we are also having this issue, our application has 1.6.1, and does use the Datadog.Trace.ClrProfiler.Managed
Are there any fixes for this yet?
I had the same issue. The workaround is to create a new registry DWORD value called LoaderOptimization
under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework
and set the value 1. Then do iisreset.
(edit: formatting)
Thanks, @prahutomo. Here is some documentation on the valid values for that setting.
Please keep in mind that forcing the loader optimization value to 1 (SingleDomain
) is a workaround. The drawback is that multiple AppDomains in the same process will no longer be able share resources. For users with many applications running in the same IIS Application Pool, this setting can increase CPU and memory usage. Please use with caution!
Btw, we are actively working (https://github.com/DataDog/dd-trace-dotnet/pull/505) on loading our tracer assemblies in a different way that doesn't interfere with the ability to share assemblies between AppDomains. This should eliminate the error without the need for this workaround.
While we are working through this. If anybody with the issue is able and willing to enable fuslogvw so that we can have a full picture of the issue you are having, that would be very helpful. Zipping up the directory and sending it to us would be greatly appreciated.
We've done several changes over the last few months to alleviate this issue, if not solve it completely. There is also the workaround of changing the LoaderOptimization
setting mentioned above.
We are closing this issue. Please re-open or create a new github issue if you encounter this again. Thanks.
Workaround still required and successful december 2023. Standalone windows forms project from back in 2010, no iis on the dev box - ergo no iisreset... VS updated earlier today... 🙈
This also fixed our problem creating assembly redirects. So it looks like it issue is still present nowadays.
Describe the bug
To Reproduce
datadog-dotnet-apm-1.6.1-x64.msi
iisreset
Runtime environment (please complete the following information):
Additional context