[ARRISEOS-47214] Video memory footprint in MemoryPressure#489
Open
ajay-ks-infosys wants to merge 1 commit intolgi-wpe-2.38-24Q3from
Open
[ARRISEOS-47214] Video memory footprint in MemoryPressure#489ajay-ks-infosys wants to merge 1 commit intolgi-wpe-2.38-24Q3from
ajay-ks-infosys wants to merge 1 commit intolgi-wpe-2.38-24Q3from
Conversation
marcin-mielczarczyk-red
requested review from
amol-virnodkar-infosys,
marcin-mielczarczyk-red and
tomasz-karczewski-red
tomasz-karczewski-red
approved these changes
Mar 20, 2025
marcin-mielczarczyk-red
approved these changes
Mar 20, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Issue:
Video memory footprint log in WPE Memory Pressure mechanism doesn't show memory usage. It's always 0 MB.
Actual results:
Video footprint is always 0 MB.
Expected results:
Video footprint should show real memory usage value.
LOG details:
journalctl -f | grep -i memorypressure