Within the last few weeks we have started seeing this error in our logs. There is a support ticket open for this issue, but I am tryting to figure out why this issue is presenting itself now. We have not made any changes to our installation or plugins.
This error is causing a performance issue for our users. Is there a known workaround?
After upgrading to v5.1.1 this is no longer an issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.