Restrict size of log file #21
Description
When an error occurs in the render loop, the log file size can grow rapidly. A recent example emitted almost 2MB of log data in about one second.
Probably the easiest option is to alter the log generation behavior to a "rolling file" scheme. By default Serilog enforces a 1GB limit, but once it hits that size it stops logging anything. A rolling file with a lower cleanup interval of a few days could be useful.
Additionally, OpenGL error callbacks are probably the most likely to cause this issue, and they're handled in the eyecandy library. A possible mitigation is to recognize and suppress repeat errors, probably for some duration. The error output from OpenGL is extremely rudimentary so it's probably sufficient to match on a combination of the flags passed to the handler (source, ID, type, etc.).