Bug: Memory reporting stuck at incorrect values after first run
Environment
- htop version: 3.5.0 (installed via Homebrew)
- macOS version: 26.4.1
Description
On the first launch, htop appears to work correctly. However, on subsequent runs, memory usage is reported incorrectly, showing a fixed value of 64.0T/36.0G regardless of actual usage.
Attempted fixes
- Manually deleted the htop config file — issue persists
- Reinstalled htop via Homebrew — issue persists
Expected behavior
Memory usage should be reported accurately on every launch.
Actual behavior
Memory usage is frozen at 64.0T/36.0G after the first run.
Please see the attached screenshot for reference.
Bug: Memory reporting stuck at incorrect values after first run
Environment
Description
On the first launch, htop appears to work correctly. However, on subsequent runs, memory usage is reported incorrectly, showing a fixed value of 64.0T/36.0G regardless of actual usage.
Attempted fixes
Expected behavior
Memory usage should be reported accurately on every launch.
Actual behavior
Memory usage is frozen at 64.0T/36.0G after the first run.
Please see the attached screenshot for reference.