Kittyfisto
commented
4 years ago This problem currently only occurs when all of the following conditions are met:
- The log file being displayed is currently being written to
- The log file contains timestamps which tailviewer is able to parse
- The log file contains some log levels which tailviewer is able to parse (and others which it cannot)
- The application writing to the log file writes a single line in multiple parts (i.e. write half of the line, flush, write second half of the line, flush)
- The line being written in multiple parts does not mention a parseable log level
- A race occurs where tailviewer is able to read the first half of the line before the application from above manages to write the second half
It is a very rare occurrence so far and has been reported by one colleague so far.
The problem itself is caused by a bug in the FilteredLogFile class and should be able to be solved there.
AdrianEggenberger
Current behaviour
Under rare circumstances, see below, tailviewer will display certain lines of a log file multiple times in succession. This can appear in various patterns, for example (N, N, N+1, N+2, etc..) or (N, N+1, N, N+1, N+2, etc...).
Expected behaviour
Tailviewer should not artificially duplicate lines and display them as they are in the origin log file.
Steps to reproduce the problem
Workaround
Whenever this problem occurs, changing any filter of the log file will cause the problem to disappear. For example simply toggling (enabling/disabling or vice versa) any non-empty filter will make this problem go away.