It is pretty clear to many folk there is some unknown 100% CPU hog in
Designer 4.02 AU1. If you have not seen it, mention it, since that is
an interesting data point.

If you have a JDK installed, you will have JConsole and jstack
installed. Find them, from a matching JDK to the JVM Designer is using,
and when you hit the CPU hog issue, execute:
jstack -l 'designer-processId'

Then paste the results into a message here. This way, we can figure out
which thread is eating all the CPU to get the devs to fix it. As of
now, they have fixed a couple of possibilities, but have no clue (Since
they are not seeing it) which process is causing the issue. So lets get
the community here to help them.

BraveBraveSirRobin's Profile:
View this thread: