MolFlow occupies all CPUs on startup

Bugs & Issues
1

I have just started to use MolFlow this week and have found the following issue only on my laptop. Other PCs are OK.

On starting the application, all 4 CPUs are immediately committed to  a collection of Molflow sub flow tasks. No geometry has been loaded and there is no activity reported on the user interface. Previous runs have only been of the demo geometries.  Repeated fresh installs of the appplication has not resolve the problem.

 

Stewart

 

Stewart

2

Hello Stewart?

What exactly does "occupy" or "commit" mean?

Spawning 4 subprocesses at start is normal. (You can set the exact number in Tools/Global Settings)

But normally they consume a negligible amount of memory and CPU load. Do you have 100% usage at Molflow startup?