SidebarMonitor 1.5.11 — the RAM breakdown, measured page by page

The RAM breakdown is measured page by page, the way RAMMap reads it — no more lumps, no more estimates.

Changed

The RAM breakdown is measured, not inferred. "Other processes" and "shared and unattributed" were two lumps that together hid ~7 of 15 GiB — and the second was a remainder, not a measurement: checked against RAMMap, ~1.5 GiB of it was kernel memory (page tables, driver-locked pages, stacks) that no performance counter reports.

The elevated helper now reads the memory manager's own page database, as RAMMap does, but sampled: one page in 16, with a rotating start, every 5 s — about 41 ms a pass on 32 GiB, every category within 1 % of a full walk, on its own timer so ETW processing never waits on it.

Hovering the RAM bar now shows only RAM actually occupied, each piece counted once:

• the coloured processes, then the next ten by name under más procesos (mstsc 401M · svchost ×94 363M …), then "and 124 more processes 1.3G";
• Windows, with its kernel broken down (pools, page tables, drivers, metadata, stacks), the file cache and the pages waiting to be written — the Windows segment on the bar grows by what the counters used to miss;
• DLLs and mapped files (in RAM once, however many processes use them) and memory shared between processes, as their own lines;
• whatever is left as unclassified — 91 MiB of 18 GiB on the dev desktop.

Without the helper, the part only the page database can split says so instead of guessing.

---

Snapshot contract v30 and helper contract v18: the agent, the elevated helper and the panel must be the same version (the installer updates all three). Two installers as before: SidebarMonitor-1.5.11.msi bundles the AMD Ryzen Master Monitoring SDK; SidebarMonitor-lite-1.5.11.msi leaves AMD's binaries out.

Not code-signed yet, so Windows SmartScreen may warn on first run — choose More info → Run anyway.