LogViewPlus has not been tested against a memory mapped file. I assume your mapped file works similar to any other file in the file system, but the file read request reads from memory rather than disk. It sounds like the file size is fixed and will not change as log entries are being written. Is this correct?
LogViewPlus monitors files by checking the size. If the file size is fixed, I don't think the zeroed out bytes would necessarily be a problem, but there would be a problem when new data is written where the data was previously empty. If the bytes of the file are pre-allocated, you may need to frequently refresh the view.
If the file size is changing, then LogViewPlus should be able to identify where new data exists and the refresh should be unnecessary.
LogViewPlus also assumes log entries are written as a whole. When LogViewPlus cannot parse a log entry, one of two situations occurs:
1. If the log entry is at the beginning of a file, it will be appended to the first complete log entry.
2. Otherwise, it will be appended to the previous log entry.
In this way, LogViewPlus cannot 'lose' data. The information can always be found by a text search or selecting the appropriate log entry, but it may not appear in the log entry grid. In the example provided, both append options will be used and the 'complete' log entry will not be parsed or available in the log entry grid.
Hope that helps,