You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm working with a user reporting a bug in OpenTelemetry .NET. It seems some file system change is triggering an IConfiguration reload which is manifesting a bug in OpenTelemetry causing some resources to be created (background threads) which aren't ever used or cleaned up. We're fixing that bug in OpenTelemetry but so far we haven't been able to figure out why that configuration reload is firing.
In the call stack we see:
Microsoft.Extensions.FileProviders.Physical.dll!Microsoft.Extensions.FileProviders.Physical.PhysicalFilesWatcher..cctor.AnonymousMethod__43_0(object state) Line 29 C#
User is on .NET 6.
User is calling Host.CreateDefaultBuilder(args) to create their host.
User isn't using any appSettings.json files.
I'm wondering if we could add some EventSource info/verbose logging inside PhysicalFilesWatcher to help troubleshoot issues in the future.
That method you are seeing seems to be spawned when a change token matches a path reported by the underlying FileSystemWatcher. I wonder if its possible that the PhysicalFilesWatcher is being disposed before the thread finish execution, not sure if that would cause problems.
What's the error message?
Do you have a consoleapp repro?
I'm working with a user reporting a bug in OpenTelemetry .NET. It seems some file system change is triggering an
IConfiguration
reload which is manifesting a bug in OpenTelemetry causing some resources to be created (background threads) which aren't ever used or cleaned up. We're fixing that bug in OpenTelemetry but so far we haven't been able to figure out why that configuration reload is firing.In the call stack we see:
Host.CreateDefaultBuilder(args)
to create their host.appSettings.json
files.I'm wondering if we could add some
EventSource
info/verbose logging insidePhysicalFilesWatcher
to help troubleshoot issues in the future.OTel issue: open-telemetry/opentelemetry-dotnet#5513
More of the stack trace
/cc @tarekgh
The text was updated successfully, but these errors were encountered: