Bug Report

After updating to v10.1.1 I'm seeing heavy CPU usage caused by check-for-changes.sh

Context

This is what I'm seeing. The CPU usage graph shows a significant increase after an update to 10.1.1 and then a sudden drop once I've downgraded back to 10.1.0. Htop reported check-for-changes.sh as the process using the most CPU on the server at the time.

This is how check-for-changes.sh behaves on 10.1.0:

There was no increase in mail traffic during that period of time so I don't believe it was caused by external factors.

What is affected by this bug?

High CPU usage.

When does this occur?

All the time on v10.1.1

How do we replicate the issue?

1. Start the server on v10.1.1
2. Done

Your Environment

• version: v10.1.1
• available RAM: 4GB
• Docker version: v20.10.8
• docker-compose version: v1.28.5

Environment Variables

ENABLE_UPDATE_CHECK=1
UPDATE_CHECK_INTERVAL=1d
AMAVIS_LOGLEVEL=0
FAIL2BAN_BLOCKTYPE=drop
ONE_DIR=1
SPOOF_PROTECTION=1
ENABLE_CLAMAV=1
ENABLE_FAIL2BAN=1
POSTFIX_MAILBOX_SIZE_LIMIT=10737420000
PFLOGSUMM_TRIGGER=daily_cron
LOGWATCH_INTERVAL=daily
REPORT_RECIPIENT=1
ENABLE_SPAMASSASSIN=1
SPAMASSASSIN_SPAM_TO_INBOX=1
MOVE_SPAM_TO_JUNK=1

Above are the env variables that were not empty that I've either changed or am not sure what the default was. I haven't changed any settings before upgrading to v10.1.1 as well as before downgrading back to v10.1.0 so this isn't caused by a settings change.

Relevant Stack Traces

I haven't noticed any abnormalities in the logs.