Description

Memory profiles for 4.9.0 CS tenants with bigger ProcessIndicator tables indicate that 70% of Central baseline heap memory (>7GB) can be linked to buildIndicatorFilter

The interesting part here is that while the table scan for PIs is only done once at startup, the profile shows that the scan is still holding on to 30% of overall memory.

This looks like we're not cleaning up memory properly. I did not attach debug data so this ticket can be public.