Thanks Brad. I have had a look at the bug report and there is nothing wrong with the JSON line that failed. This is unfortunate as it is going to make the issue harder to track down. The issue seems to be with the prior line.
What's happening here is that LogViewPlus needs to determine when a full JSON log entry has been read (keeping in mind that JSON may span multiple lines in the log file). This is done prior to JSON parsing. In this case, it is receiving a line of perfectly formatted JSON which cannot be parsed correctly because apparently something in the prior line has confused the pre-scan.
We have made a lot of JSON changes in this release and plan to make a lot more in the next release. However, in this case, I think this issue would have existed in prior versions as well. There seem to be something in the file, prior to this log line, which is causing the invalid parse.
I realize this is not always possible, but if you are able to
contact me via email and send me the log file I can probably get this turned around very quickly. Regardless, I will take a closer look at the pre-scan code to see if I can determine where the error might be.
Also - it is only the parser definition that must work with JSON primitives. This is because the conversion specifier is is a string. There should be no issue with using a conversion specifier to store a JSON object.