In reset_memory, check settings.entry_memory_load ... #58350
Conversation
…w_memory_status - it looks like the latter won't be set on Linux.
|
Tagging subscribers to this area: @dotnet/gc Issue Detailsin addition to g_low_memory_status - it looks like the latter is only set in response to low memory notifications from the OS - looks like this won't happen on Linux. This may also impact issue #52592 depending on actual memory load.
|
Maoni0
left a comment
Maoni0
left a comment
There was a problem hiding this comment.
we should make a helper function for this as we now have a few places that do exactly this.
|
Makes sense - done. |
Maoni0
left a comment
Maoni0
left a comment
There was a problem hiding this comment.
just a minor comment - I would add this as a static method in gc_heap next to all the dt_* methods since this is of the exact nature as those methods (ie, dt_high_memory_load_p)
…_high_memory_load_p.
|
/backport to release/6.0 |
|
Started backporting to release/6.0: https://github.com/dotnet/runtime/actions/runs/1193591264 |
ghost
locked as resolved and limited conversation to collaborators
2 participants
in addition to g_low_memory_status - it looks like the latter is only set in response to low memory notifications from the OS - looks like this won't happen on Linux. This may also impact issue #52592 depending on actual memory load.