audiomxd high memory allocation port allocation CPU time

You need to take some other measures in order to sort out the problem.

Mac's do not require third party AV, Protection, Cleaning or VPN to stay safe.

see > macOS - Security - Apple

1) I never heard of the GPG Suite, but it looks like protection ware that has totally invaded your Mac mini.

Uninstall GPG as per the developers instruction and test for a day or two.

2) I never hear of SENA, but it looks like it is some type of audio device paring manager.

Uninstall SENA as per the developers instruction and test for a day or two.

Sorry to hear that you have not yet found the problem.

Uninstall Audacity (3) and monitor the audiomxd activity for a day or so.

If that fixes it, maybe try the 3.7.3 ARM 64 (Apple Silicon) version.

https://www.audacityteam.org/download/mac/

This still sounds like some bad third-party software or the Mac mini attempting to connect to a bluetooth audio device.

Possibly even when the Mac mini is suppose to be in sleep mode.

https://community.jamf.com/t5/jamf-pro/audiomx-process-maxed-out/m-p/342280

https://iboysoft.com/tips/audiomxd-processor-using-so-much-ram.html

https://macsecurity.net/view/614-coreaudiod-cpu-overuse-mac

If the audiomxd numbers seem to be building when the Mac mini is sleeping at night...?

Then as a test, shut down at night and check the audiomxd numbers in the morning after startup.

EtreCheckPro is an excellent tool for finding and sorting out various problems.

Download and run the free version of EtreCheckPro, from > https://etrecheck.com/en/index.html

Then post back here with your Report, as per > How to use the Add Text Feature When Post… - Apple Community

Select the mouse that is up stairs and click the x.

Maybe something below will help you figure out what process or service is opening ports.

On macOS, ports are opened by specific processes or services that need to communicate over a network. The system uses a process called launchdto manage these processes and open ports as needed. While macOS's firewall helps manage connections, apps and services can still request and be granted access through it. 

Here's a more detailed explanation:

1. Processes Open Ports:

• When a process needs to listen for incoming connections or send outgoing requests on a specific port, it requests that port from the operating system.
• If the process is allowed to use the port, launchd (a background service) will open it and keep it open as long as the process is running or actively waiting for connections. 

2. Sharing Services:

• Sharing services like file sharing can automatically open specific ports to allow other devices on the network to connect.
• These ports are opened and closed based on whether the sharing service is enabled or disabled. 

3. Firewall:

• The macOS firewall allows or blocks connections based on applications and services, not individual ports.
• You can add an app to the firewall's allowed list to grant it access, and macOS will automatically open the necessary ports. 

4. Identifying Open Ports:

• You can use commands like lsof or nmap in the Terminal to see which ports are currently open and which processes are using them.
• For example, lsof -i :8080 will list any processes using port 8080. 

5. Closing Ports:

• You can close a port by stopping the process that's using it.
• For example, you can use kill -9 <PID> to forcefully stop a process and close its associated ports. 

Probably not the cause but should still be gone, delete this file & restart…

~/Library/LaunchAgents/com.adobe.AAM.Updater-1.0.plist

Also the high usage started on the day these were installed…

2025-05-12 EPSON Printer Driver (13.26) - Installer

2025-05-12 Epson Scan 2 (6.4.143) - Installer

2025-05-12 EPSON PC-FAX Driver (2.40) - Installer

2025-05-12 Epson Extended Service Plan (1.0.1) - Installer

2025-05-12 ET-4850 (1.0) - Installer

2025-05-12 macOS 15.5 (15.5) - Software update

2025-05-12 RosettaUpdateAuto (1.0.0.0.1.1746349326) - Install on demand

So it looks like the audiomxd CPU usage has subsided, but the creation of new ports is still off the chart.

A Google AI response says:

In macOS, various processes can create and utilize ports. While launchd is responsible for managing many system services and their associated ports, individual applications can also open ports for communication. To identify the specific process using a port, the lsof -i :<port_number> command is useful. This command lists open files and network connections, allowing you to see which process is associated with a particular port. 

for more info, see > what macOS process is creating ports

Personally I think that I would just uncheck Ports on the Activity Monitor toolbar and go on with life.

Sorry, but those Activity Monitor and Info screenshots are not really helping us see the problem.

Please post your EtreCheckPro Report, as per > https://discussions.apple.com/docs/DOC-250000211