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.
Was this Answer Record helpful?
AR# 3697
Date
02/21/2001
Status
Archive
Type
General Article
By using this website, I accept the use of cookies.
Learn more