Tracking high setroubleshootd memory use -> maybe virtualmin?

I've been tracking the high memory usage of setroubleshootd for a month or so - (my system has 1 GB memory) - memory usage can be as high as 53%.
Over weekend setroubleshootd was running at 8% (from top)
Monday morning, logged into Virtualmin and 'Refreshed System Information' - setroublehootd is now running at 53%.

(/usr/bin/python -E /usr/sbin/setroubleshootd is what is showing in Virtualmin -> Running Processes)

I have run audit2allow and pretty much cleaned up the selinux error messages (I still get problems with clamav).

It appears that various perl scripts run when refreshing system info and this somehow impacts setroubleshootd.