I have an application that utilizes the VB API to continuously regenerate the same model in Pro/E WF4. Since I am working with the same model for each regeneration, I do not close the model or erase it from memory because this would adversely affect the speed of the application. However, I have noticed that the amount of memory Pro/E consumes climbs steadily throughout each regeneration, and eventually Windows will run out of memory. I cannot figure out why Pro/E continues to consume more memory with each regeneration even though I am working with the same model each time. Has anyone else experienced this problem, or does anyone know of a solution?