Revert of Add process uptime metadata event in tracing

Revert of Add process uptime metadata event in tracing (patchset #4 id:80001 of https://codereview.chromium.org/2753133002/ )

Reason for revert:
Looks like this broke base_unittests on Linux TSan: https://uberchromegw.corp.google.com/i/chromium.memory/builders/Linux%20TSan%20Tests/builds/2916

Original issue's description:
> Add process uptime metadata event in tracing
> 
> 1. Make CurrentProcessInfo::CreationTime consistent on Linux with Win
>    and Mac implementation: return null value instead of crashing on
>    failure.
> 2. Use process_info_linux.cc in Android too, it works the same.
> 3. Add the total process uptime as meadata event in traces and
>    whitelist in filtered mode.
> 
> BUG=654667
> 
> Review-Url: https://codereview.chromium.org/2753133002
> Cr-Commit-Position: refs/heads/master@{#458799}
> Committed: https://chromium.googlesource.com/chromium/src/+/a714d7dc0f1b8ecdee128db04e24b0da1087df8a

TBR=oysteine@chromium.org,thakis@chromium.org,primiano@chromium.org,ssid@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=654667
Review-Url: https://codereview.chromium.org/2768123002
Cr-Commit-Position: refs/heads/master@{#458869}
Committed: https://chromium.googlesource.com/chromium/src/+/958a4bb090a8f57113d094be99b573c036ecb1e0

[dgozman, 2017-03-22 20:51:04]

The CQ bit was checked by dgozman@chromium.org

[dgozman, 2017-03-22 20:51:04]

Created Revert of Add process uptime metadata event in tracing

[commit-bot: I haz the power, 2017-03-22 20:51:46]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-03-22 20:53:04]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1490215864587550, "parent_rev":
"bdd9f645d6e6bb56bfa31c74c88a8842fda5d9d1", "commit_rev":
"958a4bb090a8f57113d094be99b573c036ecb1e0"}

[commit-bot: I haz the power, 2017-03-22 20:53:51]

Description was changed from

==========
Revert of Add process uptime metadata event in tracing (patchset #4 id:80001 of
https://codereview.chromium.org/2753133002/ )

Reason for revert:
Looks like this broke base_unittests on Linux TSan:
https://uberchromegw.corp.google.com/i/chromium.memory/builders/Linux%20TSan%...

Original issue's description:
> Add process uptime metadata event in tracing
> 
> 1. Make CurrentProcessInfo::CreationTime consistent on Linux with Win
>    and Mac implementation: return null value instead of crashing on
>    failure.
> 2. Use process_info_linux.cc in Android too, it works the same.
> 3. Add the total process uptime as meadata event in traces and
>    whitelist in filtered mode.
> 
> BUG=654667
> 
> Review-Url: https://codereview.chromium.org/2753133002
> Cr-Commit-Position: refs/heads/master@{#458799}
> Committed:
https://chromium.googlesource.com/chromium/src/+/a714d7dc0f1b8ecdee128db04e24...

TBR=oysteine@chromium.org,thakis@chromium.org,primiano@chromium.org,ssid@chro...
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=654667
==========

to

==========
Revert of Add process uptime metadata event in tracing (patchset #4 id:80001 of
https://codereview.chromium.org/2753133002/ )

Reason for revert:
Looks like this broke base_unittests on Linux TSan:
https://uberchromegw.corp.google.com/i/chromium.memory/builders/Linux%20TSan%...

Original issue's description:
> Add process uptime metadata event in tracing
> 
> 1. Make CurrentProcessInfo::CreationTime consistent on Linux with Win
>    and Mac implementation: return null value instead of crashing on
>    failure.
> 2. Use process_info_linux.cc in Android too, it works the same.
> 3. Add the total process uptime as meadata event in traces and
>    whitelist in filtered mode.
> 
> BUG=654667
> 
> Review-Url: https://codereview.chromium.org/2753133002
> Cr-Commit-Position: refs/heads/master@{#458799}
> Committed:
https://chromium.googlesource.com/chromium/src/+/a714d7dc0f1b8ecdee128db04e24...

TBR=oysteine@chromium.org,thakis@chromium.org,primiano@chromium.org,ssid@chro...
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=654667

Review-Url: https://codereview.chromium.org/2768123002
Cr-Commit-Position: refs/heads/master@{#458869}
Committed:
https://chromium.googlesource.com/chromium/src/+/958a4bb090a8f57113d094be99b5...
==========

[commit-bot: I haz the power, 2017-03-22 20:53:52]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/958a4bb090a8f57113d094be99b5...

[ssid, 2017-03-22 21:01:34]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/2768933002/ by ssid@chromium.org.

The reason for reverting is: The race was caused by
https://codereview.chromium.org/2736283003/
Fixed the post tasks..