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

[release/8.0] Events for IL methods without IL headers #90844

Merged
merged 6 commits into from
Aug 21, 2023

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Aug 19, 2023

Backport of #90826 to release/8.0

/cc @AaronRobinsonMSFT

Customer Impact

This failure represents a potential crash when events are enabled. It is possible the process will crash randomly without this change.

Testing

The failure was predictable and occurred regularly (> 90 %) after a change to adopt it within the runtime.

Risk

Minimal. This is adding a null check in more places that already handle returning null.

IMPORTANT: If this backport is for a servicing release, please verify that:

  • The PR target branch is release/X.0-staging, not release/X.0.

  • If the change touches code that ships in a NuGet package, you have added the necessary package authoring and gotten it explicitly reviewed.

AaronRobinsonMSFT and others added 6 commits August 19, 2023 15:08
Dynamically generated methods like UnsafeAccessor
functions are marked as IL, but don't contain an IL
header. The lack of header is an indication the IL must
be generated at runtime.
Co-authored-by: Tlakaelel Axayakatl Ceja <tlakaelel.ceja@microsoft.com>
@AaronRobinsonMSFT
Copy link
Member

@jkotas Should this instead be in release/8.0-rc1? I do need to revert #90818

@AaronRobinsonMSFT AaronRobinsonMSFT added this to the 8.0.0 milestone Aug 19, 2023
@AaronRobinsonMSFT AaronRobinsonMSFT added the Servicing-consider Issue for next servicing release review label Aug 19, 2023
@AaronRobinsonMSFT
Copy link
Member

This reverts changes from rc1 - #90818.

@jkotas
Copy link
Member

jkotas commented Aug 19, 2023

@jkotas Should this instead be in release/8.0-rc1?

The crash is triggered by combination when all of the following are true:

  • App calling Process.CreateProcess
  • Fine grained ETW or EventPipe tracing of JITed methods turned on
  • Non-default optimization settings for System.Diagnostics.Process assembly (e.g. trimmed build without R2R, optimizations disabled by debugger or profiler, etc.)

I do not think that this is RC1 blocking issue. @jeffschwMSFT ?

Copy link
Member

@jeffschwMSFT jeffschwMSFT left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

approved. we can merge when ready

@jeffschwMSFT
Copy link
Member

last changes for rc1 were late last week. so unless this is a main line issue, we should fix in rc2

@AaronRobinsonMSFT AaronRobinsonMSFT added Servicing-approved Approved for servicing release and removed Servicing-consider Issue for next servicing release review labels Aug 19, 2023
@AaronRobinsonMSFT
Copy link
Member

@jkotas or @jeffschwMSFT The CI is green, please merge when convenient.

@jeffschwMSFT jeffschwMSFT merged commit b7a3590 into release/8.0 Aug 21, 2023
@AaronRobinsonMSFT AaronRobinsonMSFT deleted the backport/pr-90826-to-release/8.0 branch August 21, 2023 14:52
@mmitche
Copy link
Member

mmitche commented Sep 20, 2023

/backport to release/8.0-rc1

@github-actions
Copy link
Contributor Author

Started backporting to release/8.0-rc1: https://github.com/dotnet/runtime/actions/runs/6242340304

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-VM-coreclr Servicing-approved Approved for servicing release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants