General Description: When a CORE Generator core GUI has finished generating a large core and control has been returned to the COREGen GUI, it still "hogs" up to 20% of the CPU time with the Java process, even though COREGen is not actively generating a module.
Solution
The only way to free up the CPU when this happens is to exit COREGen, then restart it before trying to to generate your next core.