[BUG] macOS "physicalmemory" module not working if "command" modules are set to "parallel": true

Read the FAQ first

  • I have checked the FAQ but the issue is not covered

Description

Here's my current config, it's based off the "25.jsonc" example config: config.jsonc

I wanted to display the physical memory, and the "physicalmemory" module works when called manually (fastfetch -s physicalmemory) or in the unformatted all.jsonc config (fastfetch -c all.jsonc). It wouldn't work with the config above though, and I could not figure out why. I finally figured out that it was the "command" module section that was the problem. On a whim I tried flipping "parallel" to false, and now it works. I'm not sure why this happens, and by default "parallel"is set to true, so I'm submitting this as a bug.

Version used

fastfetch 2.55.0 (aarch64)

Bug prevalence

Always

Regression

No

Installation

Package manager

Package manager

brew

Screenshots

Before:
Image

After:
Image

Configuration

System information

Features built-in

threads
vulkan
imagemagick7
chafa
zlib
sqlite3
System yyjson