https://github.com/safing/portmaster/issues/1988
---
The filterlists database is often updated when the service starts, even if the latest version is already cached in the database.
This does not affect PM’s functionality, but it unnecessarily consumes CPU resources.
**Technical explanation:**
This happens because the filterlists update check sometimes runs before the module is fully initialized.
**Steps to Reproduce:**
1. Start PM and ensure the filterlists are up to date.
2. Fully stop PM.
3. Start PM again.
**Observed result:**
PM reprocesses the filterlists cache database.
**Expected result:**
PM should update only when new data is available. Already processed data should not be reprocessed.
1ee7db6948