Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

.NET Framework publishes bad TaskWaitBegin ETW event #28

Open
rwkarg opened this issue Sep 22, 2021 · 1 comment
Open

.NET Framework publishes bad TaskWaitBegin ETW event #28

rwkarg opened this issue Sep 22, 2021 · 1 comment

Comments

@rwkarg
Copy link

rwkarg commented Sep 22, 2021

(This can't be fixed in this package but adding issue for tracking)

I attempted to hook this up with WCF services that run on .NET Framework and was able to get an IServiceBehavior configured relatively easily. Unfortunately, it appears that .NET Framework publishes the TaskWaitBegin ETW event with 5 parameters when it's defined as having 6.

This was addressed in .NET Core (dotnet/coreclr#8942) but it's not clear that the desktop/.NET Framework backport was ever completed.

The result is that the listener rejects the ETW event since it doesn't provide the 6 parameters it's expecting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant