|tagger||Simon <firstname.lastname@example.org>||Mon Jun 29 20:23:32 2015|
Rolling src/third_party/trace-viewer 1df70ec66653aad064b762bfb3f9b68900d80589..4cb7b12de28414d676090bd6.
|author||Simon <email@example.com>||Mon Jun 29 18:44:44 2015|
|committer||Simon <firstname.lastname@example.org>||Mon Jun 29 18:44:44 2015|
Fix encoding arraybuffer in base64 for upload. These weren't being encoded properly after switch to compressed traces. Also, previously we were generating uncompressed json via chrome. If you were to load a gzipped file and then attempt to upload it, you'd hit a "missing data" error. Now, we check the file type and use the appropriate path. Remail@example.com Review URL: https://codereview.appspot.com/247380043.
It provides rich analysis and visualization capabilities for many types of trace files. Its particularly good at viewing linux kernel traces (aka ftrace) and Chrome's trace_event format. Trace viewer can be embedded as a component in your own code, or used from a plain checkout to turn trace files into standalone, emailable HTML files from the commandline:
trace2html my_trace.json --output=my_trace.html && open my_trace.html
Its easy to extend trace viewer to support your favorite trace format, or add domain specific visualizations to the UI to simplify drilling down into complex data.
We welcome contributions! To hack on this code, from toplevel: ./run_dev_server
In any browser, navigate to http://localhost:8003/
Join our Google Groups: