jaydeef

I also had this issue, and can confirm that rolling back to 2.9 fixed it as well.
Seems that something is broken in 3.0.0.