Skip to content

Conversation

@PeterSolMS
Copy link
Contributor

@PeterSolMS PeterSolMS commented Nov 29, 2022

This is a refinement suggested by Maoni for earlier PR #77478 - the last_gc_before_oom flag should also not be reset by an intervening gen 1 GC.

This was noticed by Maoni due to a customer issue with spurious OOM exceptions with .NET Core 7.

@ghost ghost added the area-GC-coreclr label Nov 29, 2022
@ghost ghost assigned PeterSolMS Nov 29, 2022
@ghost
Copy link

ghost commented Nov 29, 2022

Tagging subscribers to this area: @dotnet/gc
See info in area-owners.md if you want to be subscribed.

Issue Details

This is a refinement suggested by Maoni for earlier PR#77478 - the last_gc_before_oom flag should also not be reset by an intervening gen 1 GC.

This was noticed by Maoni due to a customer issue with spurious OOM exceptions with .NET Core 7.

Author: PeterSolMS
Assignees: -
Labels:

area-GC-coreclr

Milestone: -

Copy link
Member

@Maoni0 Maoni0 left a comment

Choose a reason for hiding this comment

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

thanks Peter!

@mangod9
Copy link
Member

mangod9 commented Nov 29, 2022

This looks low risk and probably the right fix, so perhaps we should optimistically port to 7?

@PeterSolMS
Copy link
Contributor Author

Agree it's low risk, but I'll need to do some more testing on this before porting to 7 regardless.

@PeterSolMS PeterSolMS merged commit fc2bde4 into dotnet:main Nov 30, 2022
mangod9 pushed a commit to mangod9/runtime that referenced this pull request Dec 2, 2022
… 1 GC. (dotnet#78973)

This is a refinement suggested by Maoni for earlier PR#77478 - the last_gc_before_oom flag should also not be reset by an intervening gen 1 GC.

This was noticed by Maoni due to a customer issue with spurious OOM exceptions with .NET Core 7.
@ghost ghost locked as resolved and limited conversation to collaborators Dec 30, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants