-
Notifications
You must be signed in to change notification settings - Fork 5k
MetadataAggregator.GetGenerationHandle returns incorrect results for Guid heap handles #113910
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
Comments
Tagging subscribers to this area: @dotnet/area-system-reflection-metadata |
@tmat I see you have added a workaround. Are you aware of any downstream callers of this API (like Roslyn) who might be impacted by this? Did you want to suggest a fix? |
I'm not aware of any. Not high priority to fix. Would be nice to remove the workaround.
The line referenced above needs to be updated to no accumulate. Then some comments and tests need to be updated. |
Hello, I am trying to read this thread and hope to understand it so that I could start contributing this as my first task. |
Can you elaborate on |
When Like so: Baseline DLL: This is therefore not correct:
Instead the size of Guid heap in generation |
I just opened this: |
Description
guidSizes is incorrectly accumulated here:
https://github.com/dotnet/runtime/blob/main/src/libraries/System.Reflection.Metadata/src/System/Reflection/Metadata/Ecma335/MetadataAggregator.cs#L156
The size of GUID heap in aggregated metadata is the same as the size in the metadata delta where the GUID is used (unlike other heaps).
Regression?
No
Known Workarounds
See dotnet/metadata-tools#308
The text was updated successfully, but these errors were encountered: