We currently run jq 1.3 which has a bug in it that is causing most non-ascii characters to cause a fatal error mid-way the stream and leave the process with invalid json in its standard output.
I'm encountering this on stat1002 when dealing with output from kafkacat. It's valid json, but contains some kind of special character in one of the strings. Passing it through jq to perform some filtering and aggregation is crashing mid-way.
I narrowed it down to the following line. The issue seems similar to https://github.com/stedolan/jq/issues/352, which was fixed in jq 1.4 (June 2014).
{"..":"..", "user_agent":"Mozilla/5.0 (Linux; U; Android 2.3.6; es-co; XT550 Build/GRK39F) AppleWebKit/533.1 (KHTML, like Gecko) Versi�n/4.0 Mobile Safari/533.1"}
Latest version is jq 1.5 (released August 2015). We currently run jq 1.3 (released May 2013).