You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Creating a dump against some kernel implementations is committing empty pages with the page probing technique we currently use during memory enumeration. This change uses the pagemap API's in the /proc system if available - both regarding existence and permissions - along with the maps api to decide what pages contain relevant information. This results in smaller dumps and no increase in resident memory usage when collecting a dump.
Customer Impact
Customers have reported memory doubling in processes they dump. This is fatal environments such as K8s and cgroups hosting, where the process of collecting a dump often results of a OOM kill. This makes crash and ad-hoc diagnostics harder than needs be.
Testing
TBD
Risk
Low - fallback to prior code paths is enabled. Also, it's possible to explicitly disable the new behavior by setting the env var DbgDisablePagemapUse.
Creating a dump against some kernel implementations is committing empty pages with the page probing technique we currently use during memory enumeration. This change uses the `pagemap` API's in the `/proc` system if available - both regarding existence and permissions - along with the `maps` api to decide what pages contain relevant information. This results in smaller dumps and no increase in resident memory usage when collecting a dump.
Co-authored-by: Eugene Zhirov <e.zhirov@criteo.com>
Creating a dump against some kernel implementations is committing empty pages with the page probing technique we currently use during memory enumeration. This change uses the pagemap API's in the /proc system if available - both regarding existence and permissions - along with the maps api to decide what pages contain relevant information. This results in smaller dumps and no increase in resident memory usage when collecting a dump.
Customer Impact
Customers have reported memory doubling in processes they dump. This is fatal environments such as K8s and cgroups hosting, where the process of collecting a dump often results of a OOM kill. This makes crash and ad-hoc diagnostics harder than needs be.
Draft Pull Request was automatically closed for 30 days of inactivity. Please let us know if you'd like to reopen it.
ghost
locked as resolved and limited conversation to collaborators
Apr 12, 2023
This pull request was closed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backport of #79853 to release/7.0, issue #71472
Creating a dump against some kernel implementations is committing empty pages with the page probing technique we currently use during memory enumeration. This change uses the
pagemapAPI's in the/procsystem if available - both regarding existence and permissions - along with themapsapi to decide what pages contain relevant information. This results in smaller dumps and no increase in resident memory usage when collecting a dump.Customer Impact
Customers have reported memory doubling in processes they dump. This is fatal environments such as K8s and cgroups hosting, where the process of collecting a dump often results of a OOM kill. This makes crash and ad-hoc diagnostics harder than needs be.
Testing
TBD
Risk
Low - fallback to prior code paths is enabled. Also, it's possible to explicitly disable the new behavior by setting the env var
DbgDisablePagemapUse.