We have a customer continuously getting this in their error log:
I haven't been able to reproduce this issue on my side. But looking through the source code, it doesn't seem like this type of error should be reported in the error log. Perhaps it could be better handled internally (silently ignored?).
This is a problem because it uselessly fills up the error log.
2017-08-10 - A careful code review would be needed to answer the question if this has any user-visible impact, or why this occurs in the first place.