![]() ![]() So it may not bother until it is necessary. From Windows perspective, you may have plenty of memory and freeing the 7 GB will consume CPU resources. Also, if LogViewPlus is consuming 7 GB and you refresh the file, Windows will not necessarily free the 7 GB. You are reporting 7 GB, so that seems like expected behaviour. We need to double this because LogViewPlus stores a parsed and unparsed version of the message, so 6 GB. If 46 log files is 1.5 GB on the file system, this would probably be 3 GB as UTF-16. From this discussion, it seems more likely you are tailing the log files, so the number of log entries in memory far exceeds the 50 MB in the log file. If you are saying a 50 MB log file takes 7 GB in memory, that sounds like a problem that I have not yet been able to recreate. If you see my original reply, LogViewPlus is a memory intensive program. ![]() ![]() ![]() However, if my understanding of the issue is incorrect, we should keep investigating. If you are happy with that as the explanation, then I think we can close this ticket. LogViewPlus is resource starved because you are asking it to do a lot of work. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |