Comment 19 for bug 330272

Howdy all, I kinda doubt it is a problem with the database or the query itself. The messed up date makes me think of something like a corrupted pointer - most likely in the EIT code since that is the point in common for you all. A corrupted pointer will result in lots things being messed up in memory, and the malformed date format string just happens to be one of them. I'm sure there could be other reasons, but that is my theory, and that is the reason I focused on the error message reporting function rather than database accesses (because some people see completely different database errors).

I assume that if you all stop and then restart the backend, the problem goes away until next occurrence (the next time the EIT code corrupts memory, if my theory is correct)?