Hi

I recently bought the this app and I was pretty happy with it since a few days ago.
I have now the problem that the program uses about 13GB of RAM after a few minutes with only one logfile open (about 1MB size).
Can I do anything about it? Is there a setting to limit the RAM usage?

thanks
regards
Erich

Hi Erich,

Thanks for reporting this issue.  Your memory usage doesn't sound right and may be a bug.

LogViewPlus stores two copies of every log entry in memory as UTF-16 (a parsed and unparsed version) and this makes it a memory intensive application.   In other words, I would expect a 1 GB ASCII log file to take up 4 GB in memory once parsed.

This memory will only be released when a log file is closed.  Rolling log files do not release the memory.

Also, Windows will not necessarily immediately clean up memory that has been freed.  Windows will often delay memory cleanup until it is needed - which may be a long time on machines with a lot of memory.  This can make it difficult to see what is really happening. 

Can you please given me more detail on the problem you are seeing?  How are you measuring memory usage?  What is the usage before and after opening the log file?  What version of LogViewPlus are you using? 

Thanks,

Toby

Hi

Thank you for your fast reply.  It is not directly reproducible. I open a specific file in the log viewer. Size is about 1MB (not 1GB!).
Memory usage at the beginning is about 75MB (shown in Task Manager). After a few minutes (15-30) the usage jumps to about 8GB.
The Computer then does get slow, and when I close the file it immediately jumps back to about 70MB.
I will try to make a screenshot when I have reproduced it.

thanks
regards
Erich

Have you restarted the LogViewPlus process?   I am wondering if memory from previous log file loads has not been released correctly.  Or, released but not cleaned up.  

I tried a few times but have not been able to recreate.  I will keep checking.

Also, can you please make sure that you are running the latest version.  We released v2.3.2 yesterday. 

Thanks 

Toby

Hi

I have restarted the viewer and this happens after a few minutes every time.

I have taken a screenshot before and after the memory leak. In this example memory usage was "only" 519MB though, but it doesn't seem right anyway. I tried this with version 2.2.16 but I will install the new version and try it again. Are there any debug files I could provide ?

The strange thing I noticed is that the value does not increment to that 519MB, it jumps back and forth from 519MB to 22MB.
I had 5 logfiles open. They all had a max file size of 1MB.

EDIT: I noticed that when the memory usage is high, and I select the logview window, the memory usage stays the same, but after I select another window the usage immediatly drops down to normal values. It rises again to the high values after a few minutes.

EDIT2: Opened another logfile and mem usage climbed to about 10GB. It climbed with about 100MB a second till the 10gb, then I focused the log viewer and then another window, it dropped down and started climbing again immediately.

thanks
regards
Erich

Thanks for the update Erich.

The behaviour you are seeing with increasing and decreasing memory based on Window selection is expected behaviour when viewing memory in TaskManager.  To get a clearer picture of what is going on, I recommend using a more advanced tool like ProcessExplorer.   https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer  

500 MB is a lot of memory.  I have just taken a quick look and was able to recreate similar results (with larger log files, I was seeing about 400 MB).  I will investigate this further to see if we can improve things for the next release.  As mentioned earlier, part of the problem here may be Windows simply deciding to not collect freed memory. 

I also just ran LogViewPlus in a profiler with a gigabyte of log files for about 40 minutes and did not see evidence of a memory leak.

The 500 MB issue is annoying and I will look at that.  However, I am more concerned about the 8 GB issue as this is an indication of something seriously wrong.

Thanks,

Toby

Hi

Thank you for your fast help. I am using the viewer for some time now and I had no problems with our old server which runs on SUSE11. After
I switched to our new SUSE12 Server with SAMBA I encountered this problem, maybe this helps you. I am running Win10 with a network share to this server.
One other thing I noticed with the new server. Sometimes the logfiles do not get updated anymore. Neither F5 or F6(tailing) works, it does not get updated. When I close the log file and reopen it, same thing. Only when I close the whole app and reopen the app and the logfile it gets updated again and tailing works for some time.

I will try the process explorer..

EDIT: Latest version of log viewer, screenshot from process explorer before and after, hope this helps:



regards
Erich

That's interesting and could definitely be contributing to the problem.

It would be great if you could try to isolate the problem to a specific scenario.  The first step will be recreating the 8 GB issue consistently. 

Thanks, 

Toby