-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
EventPipe hangs with a shared NativeAOT library #89346
Comments
Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas Issue Details
Repro Steps
|
@LakshanF Has this been fixed? |
@LakshanF seems unlikely we can fix this in .NET 8. Can we fix the SDK to hard error if you're publishing a library with EventSource enabled? |
Works around dotnet#89346.
Works around #89346. We blocked event pipe completely in shared libraries in #90811 but: * Elinor found out the shutdown problem is actually Windows specific, so blocking Linux (our most important target) is unnecessary. * We can avoid the hang at the cost of corrupting the ongoing event pipe session by just not doing the shutdown. This can be worked around by simply stopping the event pipe session at dotnet-trace side manually. I validated the shared library scenario no longer hangs at shutdown with this. #89346 still tracks if we can do better here.
We no longer hang on windows after #91715, since we no longer call This is likely going to be the guidance for shared library trace collection and we are unlikely to have a better solution than this. |
Makes sense, thanks. I think the outstanding work item here is just docs. |
EventPipe
seems to have an issue when events are written from a shared library. Using a tool like dotnet-trace to collect trace results in a hang.Repro Steps
EventSourceSupport
property to the projectdotnet-trace collect --providers LaksDemoEventSource,Microsoft-Windows-DotNETRuntime --name MultiAotTest
The text was updated successfully, but these errors were encountered: