JSON parse failure causes blocking error in lnav conosle. #1708

lnav version
v0.14.0

Describe the bug
lnav v 0.14.0 is struggling to parse json lines in a mixed text log file. This occurs whether the file is sitting in directory or zipped.

The user get thousands of erroneous(?) JSON parse errors stop correlation & display of the remainder of other log files in the directory.

NOTE: lnav version

200.log

0.11.2 parses the same file correctly without issue (!)

The v0.14.0 console shows:

[offset: 535012] {"time": "2026-05-12 06:42:52.797", "event": "CON",
--Invalid log message: JSON line failed to parse
--parse error: invalid object key (must be a string)
==1-e06759, STRENGTH (0-9): 9",3
(right here)

v0.14.0 indicates end of line as the (right here) error spot
so I infer it is struggling to parse cr/lf/newline

This file has thousands of lines and lnav is erroring on each one. The lnav console stops correlating files past this timestamp making it unusable.

!! NOTE: lnav version lnav 0.11.2 parses the same file correctly without issue (!)

=============================================

The lines of this log file mostly resemble the line about which v0.14.0 complains:

{"time": "2026-05-11 06:35:34.531", "event": "CONNECTIVITY_WIFI_STRENGTH", "data": "SSID: aaa-e06759, STRENGTH (0-9): 9",}
{"time": "2026-05-11 06:35:49.532", "event": "CONNECTIVITY_WIFI_STRENGTH", "data": "SSID: aaa-e06759, STRENGTH (0-9): 9",}
{"time": "2026-05-11 06:36:04.529", "event": "CONNECTIVITY_WIFI_STRENGTH", "data": "SSID: aaa-e06759, STRENGTH (0-9): 9",}
{"time": "2026-05-11 06:36:19.531", "event": "CONNECTIVITY_WIFI_STRENGTH", "data": "SSID: aaa-e06759, STRENGTH (0-9): 9",}

To Reproduce

invoke lnav against attached cleansed snippet of logfile '200.log'

note: i acknowledge the input file might have malformed JSON? but it does not appear so. regardless, lnav should not halt correlating the rest of the files in a directory. IMO Worst case should be excluding an input file after some large threshold of errors occurs against that input file; and parsing the rest of the files?