Skip to content

Conversation

@forivall
Copy link

@forivall forivall commented Jul 3, 2025

I'd also like to add a column to show the raw bytes from ri_phys_footprint, but i'm not sure if i should create a new column or which existing column to use (I'm thinking of making a new VmTotal or VmPss column, which could be calculated appropriately for other operating systems)

@forivall forivall force-pushed the macos_actual_memory branch from 0646850 to 098372d Compare October 14, 2025 16:35
@dalance
Copy link
Owner

dalance commented Oct 15, 2025

I agree to add VmTotal column.

I update MSRV to fix MSRV CI failure.
So could you fix other CI failures and add VmTotal column to README.md?

@forivall forivall force-pushed the macos_actual_memory branch 2 times, most recently from a4add73 to 202a417 Compare January 6, 2026 18:41
@forivall
Copy link
Author

forivall commented Jan 6, 2026

i accidentally had a few extra commits which added support for the Env on macos - those commits had the clippy issues, as it had a quick hack to display env in json, but only in macos, due to env vars including ansi escapes (specifically LESS_TERMCAP_*, which customizes manpage colors) (honestly, the env should be formatted and escaped for all platforms, but that's a different discussion). I've moved them into another branch which i'll submit independently as a different PR.

also i think the MSRV needs to be bumped to 1.82 due to this dep update of byte-unit #841

use actual macos memory usage from libproc pid_rusage
@forivall forivall force-pushed the macos_actual_memory branch from 202a417 to 06c058f Compare January 6, 2026 19:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants