File automatically tailing

[jmhg92]

I often see that when my log file reaches a certain size (aproximately 25MB), it reloads the file and tails it after refreshing, even when "Follow tail" is disabled.

I also noticed that whenever I reach the end of the file the "Follow tail" option is enabled and stays like that until I disable it again.

EDIT:
Whenever I refreshed the file it automatically went to the end of the file and re-enabled tailing.

Bug

One issue per problem! If in doubt create a new one.
If available attach the generated log file (see wiki)

Important questions

• LogExpert Version
  1.8.0

• Windows Version
  Windows 7 x64

• Lokal file or Network
  Local File

• Used Columnizer
  No

• Is this version specific or a new problem
  Specific

Optional questions(depends on the problem):

• Continous appending log file?
  Yes

• Size of the file
  25mb

• some specific settings

• Screenshot

[fschuh]

Also noticed this happening, but on Windows 10 every time the file reloads the UI glitches and gets fully reconstructed which is extremely slow and makes it unusable.
A fix would be appreciated.

[rutschi100]

I have the same problem (Windows 10), but to a file that is on the network and to which a lot of stuff is written. I like to work with LogExpert very much but currently I can only use it for files that are rarely written to because of the bug. Use NotePad++ for the other files now (which I don't like that much).
What annoys me is not the automatic "follow tailing", but that it reloads and brings me back to the bottom of the file.

[tstreibl]

I have the same problem, using version 1.9.0.

After unchecking the follow tail option it get's reactivated by itself after a few seconds . This way I can't search something in the log. That's really a problem.

[voltz5000]

I have the same problem, using version 1.9.0.

After unchecking the follow tail option it get's reactivated by itself after a few seconds .

[RandallFlagg]

@Hirogen Issues #16 and #40 are related to this.
It doesn't explain the auto check, but it explains the jumping to the end of the file.

[Hirogen]

I'll have a look in the evening, I can reproduce #16 and #40 easily on my working machine and if those are gone, I close them

[Hirogen]

please check with the new version https://github.com/LogExperts/LogExpert/releases/tag/v.1.12.0