Got the same problem here... same platform.  We'll get it sorted out.  I suspect it's a server issue and the failure is novel enough not to show an appropriate dialog.  The fact that I can't kill the proc may mean that it's in some kind of endless loop.