I have a problem I cannot replicate in either an identically configured
test environment nor in an isolated clone of problem (production)
environment.

I suspect that the issue might be visible more often due high memory use
and load, though I never get an out of memory error.

Production is configured with a 4Gig heap and actually uses it (thanks to 8
drivers that import large XML docs via Rest). Once the - approx 50 drivers
are up and running and a daily import from each driver has been performed
RAM usage is around 4.5gb for eDirectory process.

Does anyone have a great quick and dirty way to get IDM to bloat memory
wise so I can try and rule this out? A script or a policy use that keeps
IDM busy - but doesn't crash things totally.