Bug: when log is flushed with multiple lines, `logScreen` cannot detect each json row.

[134130]

• A lot of logging framework supports internal buffering and scheduled flushing for performance.
• In my case, I'm using logScreen for golang application's visualizing. and also my golang logging framework, zerolog, buffers logs and flush multiple lines at a time.
• In this case, logScreen's log.message does not indicates only one JSON line, but multiple JSON lines joined with \n character.