Yes, this was being discussed on the alpha team list for betas 10 and 11, we are aware that it still happens occasionally. Too bad, because it's a real show-stopper.

I haven't had it happen since beta9, but maybe I'm just lucky.

And I still can't locate the existing bug number in the internal database.