Escape name and category of trace events.
Some calls to trace an event pass a source location as name
(e.g. in BeginFrameTracker::Start). On Windows, these location paths are
separated by backslashes which were not escaped when saving as JSON.
This lead to unparsable trace files created by chrome://tracing.
R=primiano@chromium.org
BUG=599176
TEST=TraceEventTestFixture.NameAndCategoryEscapedIfNeeded
Review URL: https://codereview.chromium.org/1870563002
Cr-Commit-Position: refs/heads/master@{#385848}
CrOS-Libchrome-Original-Commit: c3074fbaf4ed55a4ebae511cb2bc943d0af532f9
2 files changed