Bug: After initial sync and compaction, electrs has constant CPU activity and DB size grows and shrinks 56GiB to 61GiB to 56Gib

**Describe the bug** Bug: After initial sync and compaction, electrs has constant CPU activity and DB size grows and shrinks 56GiB to 61GiB to 56Gib. There are no new blocks during this time. This happens on half of my computers running electrs, not at all on other half (normal behaviour of only CPU activity when a new block comes in) Is there a way to diagnose what electrs is doing with all this CPU and NVME activity ? It seems like it is just compacting a portion of the db over and over **Electrs version** 0.11.0 **To Reproduce** After first run of electrs with successful completion of index and compaction, on next running of electrs, the bug occurs **Expected behavior** Run electrs after first index, only have CPU activity when a new block comes in or when it is catching up for blocks since last time run. **Configuration** log INFO shows no activity while CPU is 80-90% and the NVME is getting warm and the db folder grows from 56GiB to 61GiB then back to 56Gib and that just cycles forever log DEBUG shows lots of mempool activity <details> ``` type error message here ``` </details> **System running electrs** **Electrum client** **Additional context** Add any other context about the problem here.