Make ResourceTimingInfo RefCounted.

Make ResourceTimingInfo RefCounted.

Currently, ResourceTimingInfo's creation only returns a std::unique_ptr.
However, a ref-counted ResourceTimingInfo instance is needed so that a
single instance can be shared by multiple owners. The reason that this
new feature is requested is because now we expose PerformanceNavigationTiming
in a timely manner, which entails dynamically updating PerformanceNavigationTiming
instance as more information gets collected. One ResourceTimingInfo instance will
be held by a ResourceFether and a PerformanceNavigationTiming instance at the same
time. ResourceFether will keep updating ResourceTimingInfo while
PerformanceNavigationTiming consumes it. Therefore, making ResourceTimingInfo
ref-counted is needed.

BUG=701113
Review-Url: https://codereview.chromium.org/2747933002
Cr-Commit-Position: refs/heads/master@{#456865}
Committed: https://chromium.googlesource.com/chromium/src/+/2e016fcf6b3eae31983727f7f768d7a9b841ecf2

[sunjian, 2017-03-13 21:35:07]

Description was changed from

==========
BUG=
==========

to

==========
Make ResourceTimingInfo RefCounted.

Currently, ResourceTimingInfo's creation only returns a std::unique_ptr.
However, a ref-counted ResourceTimingInfo instance is needed so that a
single instance can be shared by multiple owners. The reason that this
new feature is requested is because now we expose PerformanceNavigationTiming
in a timely manner, which entails dynamically updating
PerformanceNavigationTiming
instance as more information gets collected. One ResourceTimingInfo instance
will
be held by a ResourceFether and a PerformanceNavigationTiming instance at the
same
time. ResourceFether will keep updating ResourceTimingInfo while
PerformanceNavigationTiming consumes it. Therefore, making ResourceTimingInfo'
ref-counted is needed.

BUG=701113
==========

[sunjian, 2017-03-13 21:42:20]

Description was changed from

==========
Make ResourceTimingInfo RefCounted.

Currently, ResourceTimingInfo's creation only returns a std::unique_ptr.
However, a ref-counted ResourceTimingInfo instance is needed so that a
single instance can be shared by multiple owners. The reason that this
new feature is requested is because now we expose PerformanceNavigationTiming
in a timely manner, which entails dynamically updating
PerformanceNavigationTiming
instance as more information gets collected. One ResourceTimingInfo instance
will
be held by a ResourceFether and a PerformanceNavigationTiming instance at the
same
time. ResourceFether will keep updating ResourceTimingInfo while
PerformanceNavigationTiming consumes it. Therefore, making ResourceTimingInfo'
ref-counted is needed.

BUG=701113
==========

to

==========
Make ResourceTimingInfo RefCounted.

Currently, ResourceTimingInfo's creation only returns a std::unique_ptr.
However, a ref-counted ResourceTimingInfo instance is needed so that a
single instance can be shared by multiple owners. The reason that this
new feature is requested is because now we expose PerformanceNavigationTiming
in a timely manner, which entails dynamically updating
PerformanceNavigationTiming
instance as more information gets collected. One ResourceTimingInfo instance
will
be held by a ResourceFether and a PerformanceNavigationTiming instance at the
same
time. ResourceFether will keep updating ResourceTimingInfo while
PerformanceNavigationTiming consumes it. Therefore, making ResourceTimingInfo
ref-counted is needed.

BUG=701113
==========

[sunjian, 2017-03-13 21:44:27]

sunjian@chromium.org changed reviewers:
+ haraken@chromium.org, ksakamoto@chromium.org, panicker@chromium.org,
yoav@yoav.ws

[sunjian, 2017-03-13 21:44:27]

The patch is separated out from https://codereview.chromium.org/2647643004/.
Please take a look!

[sunjian, 2017-03-13 21:44:33]

The CQ bit was checked by sunjian@chromium.org

[commit-bot: I haz the power, 2017-03-13 21:45:22]

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-13 21:45:23]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-03-13 21:45:24]

No L-G-T-M from a valid reviewer yet. 
CQ run can only be started by full committers or once the patch has
received an L-G-T-M from a full committer.
Even if an L-G-T-M may have been provided, it was from a non-committer,
_not_ a full super star committer.
Committers are members of the group "project-chromium-committers".
Note that this has nothing to do with OWNERS files.

[panicker, 2017-03-13 22:43:07]

The CQ bit was checked by panicker@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-03-13 22:44:05]

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

[panicker, 2017-03-13 22:44:30]

lgtm

[commit-bot: I haz the power, 2017-03-14 00:27:38]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-03-14 00:27:39]

Dry run: Try jobs failed on following builders:
  linux_android_rel_ng on master.tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/linux_androi...)

[haraken, 2017-03-14 03:06:44]

LGTM

[sunjian, 2017-03-14 20:58:28]

The CQ bit was checked by sunjian@chromium.org

[commit-bot: I haz the power, 2017-03-14 20:59:14]

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-14 22:25:23]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1489525108524640, "parent_rev":
"d028bb17b6b7fd22c69e1a788a0e8c0dbc57ca30", "commit_rev":
"2e016fcf6b3eae31983727f7f768d7a9b841ecf2"}

[commit-bot: I haz the power, 2017-03-14 22:26:07]

Description was changed from

==========
Make ResourceTimingInfo RefCounted.

Currently, ResourceTimingInfo's creation only returns a std::unique_ptr.
However, a ref-counted ResourceTimingInfo instance is needed so that a
single instance can be shared by multiple owners. The reason that this
new feature is requested is because now we expose PerformanceNavigationTiming
in a timely manner, which entails dynamically updating
PerformanceNavigationTiming
instance as more information gets collected. One ResourceTimingInfo instance
will
be held by a ResourceFether and a PerformanceNavigationTiming instance at the
same
time. ResourceFether will keep updating ResourceTimingInfo while
PerformanceNavigationTiming consumes it. Therefore, making ResourceTimingInfo
ref-counted is needed.

BUG=701113
==========

to

==========
Make ResourceTimingInfo RefCounted.

Currently, ResourceTimingInfo's creation only returns a std::unique_ptr.
However, a ref-counted ResourceTimingInfo instance is needed so that a
single instance can be shared by multiple owners. The reason that this
new feature is requested is because now we expose PerformanceNavigationTiming
in a timely manner, which entails dynamically updating
PerformanceNavigationTiming
instance as more information gets collected. One ResourceTimingInfo instance
will
be held by a ResourceFether and a PerformanceNavigationTiming instance at the
same
time. ResourceFether will keep updating ResourceTimingInfo while
PerformanceNavigationTiming consumes it. Therefore, making ResourceTimingInfo
ref-counted is needed.

BUG=701113

Review-Url: https://codereview.chromium.org/2747933002
Cr-Commit-Position: refs/heads/master@{#456865}
Committed:
https://chromium.googlesource.com/chromium/src/+/2e016fcf6b3eae31983727f7f768...
==========

[commit-bot: I haz the power, 2017-03-14 22:26:08]

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