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.

Sign up for GitHub

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

Jump to bottom

GC information through Profiling APIs is too heavy to use #6847

Closed
lt72 opened this issue Oct 18, 2016 · 2 comments
Closed

GC information through Profiling APIs is too heavy to use #6847

lt72 opened this issue Oct 18, 2016 · 2 comments
Assignees
@noahfalk
Labels
area-Diagnostics-coreclr
Milestone
Future

Comments

@lt72
Copy link
Contributor

lt72 commented Oct 18, 2016

GC information is coupled with expensive object tracking information making cheap GC events exposed from Profiling APIs unusable.
Simple information, such as Start/Stop/Generation/Memory Reclaimed should be more readily available.
@lt72
Copy link
Contributor Author

lt72 commented Nov 8, 2017

Please let us know if this is still a concern and what the time frame is that you care about.

@msftgits msftgits transferred this issue from dotnet/coreclr Jan 31, 2020
@msftgits msftgits added this to the Future milestone Jan 31, 2020
@davmason
Copy link
Member

Fixed with dotnet/coreclr#24156

@ghost ghost locked as resolved and limited conversation to collaborators Dec 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@noahfalk noahfalk

Labels
area-Diagnostics-coreclr
Projects
None yet
Milestone
Future
Development

No branches or pull requests
4 participants
@noahfalk @lt72 @msftgits @davmason