Sometimes appended file is reloaded completely instead of updated

[petsuter]

Usually when a log file is appended to, the only visible update is that the new lines are shown.

But sometimes (almost always with larger files?) the entire file seems to get reloaded (with a progress bar in the statusbar) and the line/text columns are removed and re-added. This is hugely distracting and slow and makes the program useless for such logfiles where this happens constantly.

[Hirogen]

This can be tested with continous written loglines (50-100+) per second in very large-Logfiles (800+ mb), that are opend via a network drive.

[zarunbal]

Thanks I'll try to reproduce this problem.

@Hirogen does this behavior only happen after 800+ MB files? How big (characters and Encoding) are your lines (avg, just a rough estimation). Have you some special settings (highlighting, Actions, Buffer Sizes, ...)

[Pipecity]

I'm also seeing this behavior but on smaller files as well. I'm using default settings.
Really frustrating.

[isosphere]

I've had this issue, or perhaps a different issue: A small file (~23 MB) would take awhile to load, then upon loading it would be reloaded from scratch. The result is that the file is just continuously reloading.

I've solved the problem in my particular case by selecting "Use legacy file reader" under "Memory/CPU".

[nicolas-raoul]

Same symptoms (text and "Line"/"Text" coluns reloading constantly) with a local 200KB (yes very small) file on the C: drive, updated every 5 seconds, on Windows 10 Pro 1803 / freshly installed LogExpert 1.6.13 with default settings.

The workaround suggested at #16 (comment) solved the problem (now only the few new lines appear and the existing content moves smoothly).

[Hirogen]

Same symptoms (text and "Line"/"Text" coluns reloading constantly) with a 200KB (yes very small) file updated every 5 seconds on Windows 10 Pro 1803 / freshly installed LogExpert 1.6.13 with default settings.

Can you reproduce the problem with the 200kb file all the time it is loaded?

[nicolas-raoul]

@Hirogen Yes I just switched "Use legacy file reader" off, closed LogExpert, reopened it, and the problem reproduced. Closed and reopened again, it reproduced again. The file is still under 1MB.

[Pr0metheus2]

I can reproduce same problem. Please see YT video. Could be problem linked to bug with multiple log files on network folder with extension .log, .log.1, .log.2 etc.? Even "Use legacy file reader" is ON.
https://youtu.be/eIlX-Jr2Tzc

[RandallFlagg]

@Hirogen
This issue still exists. In order to reproduce it one needs to write more than one line before the thread does polling.

The code goes into the if instead of into the else:

if (newSize < FileSize || _isDeleted)
{
...
    if (!IsMultiFile)
    {
        OnLoadFile(new LoadFileEventArgs(_fileName, 0, true, _fileLength, true));
    }
...
}
else
{
...
    OnFileSizeChanged(args);
...
}

The solution will be to rewrite this part of the code and get rid of the thread and use File System Watcher

[Hirogen]

File System Watcher needs a thorough and precise implementation, otherwise it will be more of a problem then a solution.

https://weblogs.asp.net/ashben/31773
https://stackoverflow.com/questions/15519089/avoid-error-too-many-changes-at-once-in-directory/35432077#35432077