We were able to reproduce this behaviour, we assigned ticket no. J-1724 to this bug.
It is an issue about being too hasty

The program does not respond correctly if a 3D visualisation is deleted while it is still being initialised:
You are still in the process of showing the selected 3D visualisation, and during that process you want to switch to a different design function (which automatically clears the workspace). So the program tries to close the 3D visualisation it is just busy putting it on screen. Which leads to a race-condition / infinite loop.
It is going to be a bit of an issue to allow a neat cancelation during initialisation. In the meantime, I advise to have a bit of patience and wait for the 3D visualisation to show before closing it again.