Mine did this too. After a while it all settled down and seems to be working OK again too - I think. Seems to be related to some fixes\changes in 19.5 - see Changelog v0.19.5. Though not quite sure how the explanation relates to these error messages - maybe somebody can explain in less tech terms how they are related.