-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Remove startup byte[] allocation in EventSource #32276
Conversation
8a1f223
to
1408ce7
Compare
src/libraries/System.Private.CoreLib/src/System/Diagnostics/Tracing/EventSource.cs
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks Stephen!
src/libraries/System.Private.CoreLib/src/System/Diagnostics/Tracing/EventSource.cs
Show resolved
Hide resolved
Only occurs once and is then cached, but it's hit on startup, and may as well remove it.
1408ce7
to
00a5da6
Compare
I had to put the old code back under ifdef to not break the downlevel assembly. What is that library for? |
My understanding is that ES_BUILD_STANDALONE define is to build this nuget package, which was offered as an out-of-band release vehicle for some EventSource functionality before it was available in the official runtime release. At this point I don't think we release this thing any more and I doubt there is any purpose to keeping the define or the project in our source. @brianrob - does that sound right? |
We're still building https://github.com/dotnet/runtime/tree/master/src/libraries/Microsoft.Diagnostics.Tracing.EventSource.Redist. If we can remove that, great :) |
It's actually this package: https://www.nuget.org/packages/Microsoft.Diagnostics.Tracing.EventSource.Redist/ You're right that it's an out-of-band release vehicle for EventSource - specifically for desktop, since it's hard to get fixes to desktop customers in a timely manner. I would recommend not getting rid of this, as the problem of shipping fixes to desktop customers isn't likely to go away, and this is a thing that comes up every once and while, and is always a high-priority thing when it comes up. The last time it was a big deal, we didn't have a way to produce a package, and thus I ended up doing the work to add it here. |
Only occurs once and is then cached, but it's hit on startup, and may as well remove it.
cc: @noahfalk