[traceviewer] - trace2html can parse a .json.gz file but chrome://tracing fails

[itaych]

https://drive.google.com/open?id=1lIy6lSWU700PW1oeZrfdaFVGjI4E2g2A

This is a .json.gz tracing file generated by a Linux multithreaded application and compressed during runtime using boost::iostreams::gzip.
trace2html can parse this file directly and convert it to a working html. But in our workflow we typically want to open it directly in a chrome://tracing tab.

• If I gunzip the file, chrome://tracing can open the result .json.
• If I gunzip the file and gzip it again from the Linux command line, chrome://tracing can open the recompressed file directly.
• If I try to open the original file directly in chrome://tracing then it looks like most of the file has been truncated with no error message. (Tested Chrome version is Version 74.0.3729.157 (Official Build) (64-bit) on both Ubuntu 16.04 and Windows 7.)

I've reported this to the Chrome developers using the "report an issue" feature but received no response, so I'm trying my luck here. Thanks :)