I have a single log file open, and:



Why?

Thanks for the clarification Johnny.  Not sure where I got 'remote' from.  :-)

Given the memory you have available, you should be able to open a 1 GB file and work with it.  The issue here is the amount of memory consumed after an extended period of time.  It is not yet clear why the memory is spiking, but I am not sure you should be concerned about just opening and working with a large amount of data.  I am able to do this locally without issue.  I think the problems discussed here are more likely due to the accumulation of actions taken throughout the day.

There are several things we can do with memory management which will effectively be a trade-off of less memory for more CPU similar to the memory compression idea (a good one!  :-).  Currently, we aim to save CPU cycles, but we will be revisiting this soon. 

LogViewPlus consumes memory when opening and parsing the log file.  There is a lot of work that happens here and a lot of excess memory may be allocated which can then be reclaimed.  After parsing, everything else done by the application should be pretty trivial from a memory perspective.

Hope that helps,

Toby

Ok, TYVM, I'm just happy that I reported it and you're now aware of it. =)

If you'd like me to beta test any relevant changes, I'd be happy to.

One quick question (or request if it doesn't already exist): many similar log viewers or other apps (one example coming to mind is Discord) will have a feature that draws a horizontal line between where you left off since last viewing:



I guess maybe it just monitors if the window/tab has focus. That would be super handy when viewing logs as well, if it drew a line across the row above where you left off, so it's much faster to get your bearings when you come back.

Thanks for bringing this to our attention.  It's a problem I would love to get to the bottom of, but the first step is to recreate locally.  LogViewPlus is memory intensive, but in the next few months we will be revisiting this.  I suspect the rewrite will address this issue if we are not able to resolve it before then.  I will let you know when a beta release is available.

I can see where the line idea is helpful for chat applications, but I am not sure it would help with log files.  It is often not clear which messages have been 'read'.  LogViewPlus will tail log files and some applications can produce a lot of data.  So just because a message was displayed doesn't mean it was seen.

I think the closest thing we have to this feature is the "Clear Entries" command (F4).  This will clear all log entries from the view.  All log entries displayed after this action will therefore be new.

Hope that helps,

Toby