Hi
I've set a new particle system's Start lifetime to Infinity and got these errors.
Changing it to a number stops the errors.
Both in editor (start simulating gives the errors, stopping stops them) and in game (via play).

It still happens in 5.5, I think it may occur when you have a particle system with small particles far from the camera, and the render cannot process them because they have a size of 0

I suggest to make a script which disable/enable emission when the particls are close or far from the camera

This is not fixed. Unity 2017.1 patch 1. This error appears when try to scale particles with hierarchy scale type selected.

Okay, since I had just made slight modification to my code before getting this error, I went back and took another look at what I did. I had accidentally //'d the line where I calculate the denominator for the velocity calculation. Since I Mathf.Clamp the velocity before assigning it, the game continued to play in spite of the error, though presumably always at maximum velocity.

Once I fixed it, those errors disappeared.

My bad. Hopefully this little bit of information will help someone else find their error faster.

I use Unity 5.6, I have made no major changes to my code, and I just started getting these errors.
The game seems to run okay, but the console is becoming loaded with these messages.
I have no particle systems in my game.
With most errors, you can click on it to find out where it's occurring. This tells you NOTHING! I don't even know what it MEANS!
If this is a bug in Unity, I can wait for a fix. If there is actually something wrong with my code, I have to be able to fix it before I can publish my game.

Not fixed.

Just had what looks like this error, spat out 214 console errors and my FPS went down to 2 for a few seconds, heres a screenshot: http://prntscr.com/eezrbq

This is unity version 5.50f3! :/

I just got this error in 5.5.0f3!
Last change to project was adding Steamworks.NET. No idea why it suddenly happens.

I'm having troubles getting a clear repro, but I think this still might exist in 5.5.0b11. Will try and narrow it down a bit more (maybe objects w/ scale = 0 issues).

Reproduced on 5.4f3