I never had this problem until now. I was thinking it had something to do with patch 1.19a