Physical Ram Usage is showing wrong value

[corechunk]

Code of Conduct

• I agree to follow this project's Code of Conduct

What happened?

fastfetch showing that i used 37% but omp shows 28% ram usage ...... ?!

i used

{
          "background": "#378504",
          "foreground": "#f2f3f8",
          "invert_powerline": true,
          "style": "powerline",
          "powerline_symbol": "\ue0b2",
          "properties": {
            "display_mode": "compact"
          },
          "template": " \ue266 {{ printf \"%.0f\" .PhysicalPercentUsed }}% ",
          "type": "sysinfo"
}

Theme

1_prime.omp.json

What OS are you seeing the problem on?

Linux

Which shell are you using?

bash

Log output

_,met$$$$$gg.           DISTRO 󰑃  Debian GNU/Linux 13 (trixie) x86_64
     ,g$$$$$$$$$$$$$$$P.       │ ├ 󰑃  Linux 6.12.41+deb13-amd64
   ,g$$P""       """Y$$.".     │ ├󰏖 󰑃  2286 (dpkg)
  ,$$P'              `$$$.     │ └ 󰑃  bash 5.2.37
',$$P       ,ggs.     `$$b:     DE/WM 󰑃  Hyprland 0.49.0 (Wayland)
`d$$'     ,$P"'   .    $$$     │ ├󰀻 󰑃  Tokyonight-Dark [Qt], Flat-Remix-Blue-Dark [GTK3]
 $$P      d$'     ,    $$P     │ ├ 󰑃  Bibata-Modern-Ice (24px)
 $$:      $$.   -    ,d$$'     │ ├ 󰑃  FantasqueSansMNFM-Bold (14pt)
 $$;      Y$b._   _,d$P'       │ └ 󰑃  kitty 0.41.1
 Y$$.    `.`"Y$$$$P"'          󰌢 SYSTEM 󰑃  HP Pavilion Laptop 15-eg1xxx
 `$$b      "-.__               │ ├󰻠 󰑃  11th Gen Intel(R) Core(TM) i5-1155G7 (8) @ 4.50 GHz
  `Y$$b                        │ ├󰻑 󰑃  Iris Xe Graphics
   `Y$$.                       │ ├󰍹 󰑃  1920x1080 @ 60Hz
     `$$b.                     │ ├󰾆 󰑃  2.75 GiB / 7.52 GiB (37%)
       `Y$$b.                  │ ├󰓡 󰑃  0 B / 7.63 GiB (0%)
         `"Y$b._               │ ├󰅐 󰑃  1 hour, 24 mins
             `""""             │ └󰍹 󰑃  1920x1080 @ 60Hz
                                AUDIO 󰑃  Tiger Lake-LP Smart Sound Technology Audio Controller Speaker
                                                                        


╭─   netchunk  ~                                                                                                                               64ms   bash   28%   3:45 PM 
╰─➜

[Edu4rdSHL]

It isn't a bug. fastfetch counts cached memory as "used", which is true in the sense that it's being used, but that memory can be reclaimed at any time, so it shouldn't be counted there. See d6c1ff9

Edit: it seems to be an unrelated issue to the commit I linked as it's happening on percentages instead of raw memory values on GB. Dismiss it.

[sanki92]

@JanDeDobbeleer I've submitted a PR #6850 that fixes this issue.

The problem was that the memory calculation didn't account for available memory properly. Now it correctly shows 37% matching other system tools.

Tests included ✓

[sanki92]

It isn't a bug. fastfetch counts cached memory as "used", which is true in the sense that it's being used, but that memory can be reclaimed at any time, so it shouldn't be counted there. See d6c1ff9

Edit: it seem

@Edu4rdSHL Actually, the issue is the opposite - oh-my-posh is underreporting memory usage (28% vs the correct 37%).

Standard Linux tools (fastfetch, htop, free) all use: (Total - Available) / Total × 100

From the issue: 7.52 GiB total - 4.74 GiB available = 36.96% used ✓ (matches fastfetch)

The commit d6c1ff9 you mentioned was for raw GB display in themes, not percentage calculations.

I've submitted a PR to fix this. 👍

[Edu4rdSHL]

It isn't a bug. fastfetch counts cached memory as "used", which is true in the sense that it's being used, but that memory can be reclaimed at any time, so it shouldn't be counted there. See d6c1ff9

Edit: it seem

@Edu4rdSHL Actually, the issue is the opposite - oh-my-posh is underreporting memory usage (28% vs the correct 37%).

Standard Linux tools (fastfetch, htop, free) all use: (Total - Available) / Total × 100

From the issue: 7.52 GiB total - 4.74 GiB available = 36.96% used ✓ (matches fastfetch)

The commit d6c1ff9 you mentioned was for raw GB display in themes, not percentage calculations.

I've submitted a PR to fix this. 👍

Hi, yes, I edited the comment to clarify my fault. Thanks for the PR!