Comment 14 for bug 1254555

Alan, the root cause of the issue is the ordering of policy loading and extension framework loading. It was not fixed in general, but so far no symptoms were seen after this fix was applied.

So I'm changing status to 'fix committed'