Mars the Infomage - 2013-01-28

On the off-chance that someone will want to work on this project again...

Seeing this behavior with 1.5.0 reading SAS logs (20-40mb on average. the log file is permanenly write-locked, and updated semi-randomly - can have hundreds of lines a second, can have nothing for 10 minutes). seems to happen more often when the file is read from a UNC file share (e.g. \\machine\folder\log.log)

The file is then continuously (?) cycled - once the end of the log is reached, it starts displaying it again - the process takes long enough that I haven't waited for it to happen more than once. Since the stop button has no effect per the other bug, the only way to fix this is to close tracelog completely and start a new instance