Skip to content

Memory usage in CG Slice path could be 0 #6110

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

Merged
merged 6 commits into from
Mar 14, 2025

Conversation

makazeu
Copy link
Contributor

@makazeu makazeu commented Mar 14, 2025

Fixes #6099.

Memory usage in /sys/fs/cgroup/*.slice/memory.current could be 0.

root@ubuntu:~# for file in /sys/fs/cgroup/*.slice/memory.current; do echo "$file: $(cat $file)"; done
/sys/fs/cgroup/system.slice/memory.current: 184750080
/sys/fs/cgroup/user.slice/memory.current: 0
Microsoft Reviewers: Open in CodeFlow

@makazeu makazeu requested a review from a team as a code owner March 14, 2025 04:49
@makazeu makazeu changed the title Memory usage in Slice path could be 0 Memory usage in CG Slice path could be 0 Mar 14, 2025
@evgenyfedorov2 evgenyfedorov2 merged commit 2bb24da into dotnet:main Mar 14, 2025
6 checks passed
@makazeu makazeu deleted the cg-slice-memory-fix branch March 14, 2025 07:13
peterwald pushed a commit to peterwald/extensions that referenced this pull request Mar 14, 2025
* Memory usage in Slice path could be 0

* Update memory usage test to handle zero values and refine method name

* Update error message for memory usage exception to clarify non-negative expectation

* Merge test cases
@github-actions github-actions bot locked and limited conversation to collaborators Apr 13, 2025
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.

Crash with /sys/fs/cgroup/machine.slice/memory.current being 0
3 participants