We had a recent issue, which should have been fixed by now. Are you seeing the same behavior using the latest nightly build?