If you try to view the logs in the web gui it then causes some kind of error and stops mining for a bit in the command line and the gui
It then restarts and the number of shares and times mined resets...
I know there is an exception throw when you navigate away from the log, which doesn't harm anything as far as I can see, but I need to handle the websocket session termination better. I haven't seen any errors when actually viewing the log.. Or any disruption in stats, but I'll play around and see if I can replicate.
Could you provide the error message and stack trace that you are seeing.