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

[Pinned Object Heap] DacpAllocData needs to support Pinned Object Heap #13735

Closed
VSadov opened this issue Nov 5, 2019 · 7 comments
Closed

[Pinned Object Heap] DacpAllocData needs to support Pinned Object Heap #13735

VSadov opened this issue Nov 5, 2019 · 7 comments

Comments

@VSadov
Copy link
Member

VSadov commented Nov 5, 2019

DacpAllocData has a field for allocated LOH bytes.
It needs to handle POH somehow - include it in the number or have a separate field.

struct MSLAYOUT DacpAllocData : ZeroInit<DacpAllocData>
{
    CLRDATA_ADDRESS allocBytes;
    CLRDATA_ADDRESS allocBytesLoh;
};
@VSadov VSadov self-assigned this Nov 5, 2019
@msftgits msftgits transferred this issue from dotnet/coreclr Jan 31, 2020
@msftgits msftgits added this to the 5.0 milestone Jan 31, 2020
@ghost
Copy link

ghost commented May 5, 2020

Tagging subscribers to this area: @tommcdon
Notify danmosemsft if you want to be subscribed.

@tommcdon tommcdon added the p1 label May 5, 2020
@tommcdon
Copy link
Member

tommcdon commented May 5, 2020

@VSadov do you plan on addressing this issue in the Net 5.0 timeframe?

@VSadov
Copy link
Member Author

VSadov commented May 5, 2020

Yes, the plan is to address this for 5.0
From the feedback I hear that this should be addressed sooner rather than later. I'll try to look at #13736 first, unless this needs to be handled at the same time.

@davmason
Copy link
Member

DacpAllocData is currently unused in SOS, to determine alloc data SOS scans the GC heap and does not rely on the runtime to report it (see https://github.com/dotnet/diagnostics/blob/b27e6ad70f01ff638eef02dac50de4bebfcaa40e/src/SOS/Strike/eeheap.cpp#L768-L850).

@leculver or @noahfalk do you know of any use for DacpAllocData/DacpGenerationAllocData/ISOSDacInterface::GetHeapAllocData? I suspect these are unused and do not need updating.

@noahfalk
Copy link
Member

I'm not aware of any specific usage and I think its fine to consider it unused.

@davmason
Copy link
Member

Thanks Noah. Closing this issue out and leaving the API as-is. If anyone knows of a use, feel free to reopen.

@leculver
Copy link
Contributor

Sorry my internet has been really spotty all day. @davmason I can confirm that ClrMD doesn't use that structure, and doesn't call "GetThreadAllocData" which is the only function that uses it.

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

No branches or pull requests

6 participants