|
|
Created:
3 years, 10 months ago by Taylor Brandstetter Modified:
3 years, 10 months ago Reviewers:
pthatcher1 CC:
webrtc-reviews_webrtc.org, tterriberry_mozilla.com Target Ref:
refs/heads/master Project:
webrtc Visibility:
Public. |
DescriptionRelanding: Use std::unique_ptr instead of rtc::scoped_refptr in AsyncInvoker.
The AsyncClosures only ever have one thing referencing them, so they
should be using std::unique_ptr to manage ownership. Maybe this code was
written before std::unique_ptr was available.
Originally reverted because it made a change to ScopedMessageData
that wasn't backwards compatible, and applications using the rtc::Thread
infrastructure may be using it.
BUG=None
NOTRY=True
Review-Url: https://codereview.webrtc.org/2689233003
Cr-Commit-Position: refs/heads/master@{#16684}
Committed: https://chromium.googlesource.com/external/webrtc/+/a8bc1a1f63ca8b899526b5af0203264f8f281772
Patch Set 1 #Patch Set 2 : Fixing memory leak (forgot delete statement) #Patch Set 3 : Making changes to ScopedMessageData backwards compatible #Patch Set 4 : . #
Messages
Total messages: 34 (20 generated)
deadbeef@webrtc.org changed reviewers: + pthatcher@webrtc.org
Something I noticed while working on the other CL that made me scratch my head.
Ping
lgtm
The CQ bit was checked by deadbeef@webrtc.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.webrtc.org/...
Description was changed from ========== Use std::unique_ptr instead of rtc::scoped_refptr in AsyncInvoker. The AsyncClosures ever only have one thing referencing them, so they should be using std::unique_ptr to manage ownership. Maybe this code was written before std::unique_ptr was available. BUG=None ========== to ========== Use std::unique_ptr instead of rtc::scoped_refptr in AsyncInvoker. The AsyncClosures only ever have one thing referencing them, so they should be using std::unique_ptr to manage ownership. Maybe this code was written before std::unique_ptr was available. BUG=None ==========
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: linux_memcheck on master.tryserver.webrtc (JOB_FAILED, http://build.chromium.org/p/tryserver.webrtc/builders/linux_memcheck/builds/5349)
The CQ bit was checked by deadbeef@webrtc.org
The patchset sent to the CQ was uploaded after l-g-t-m from pthatcher@webrtc.org Link to the patchset: https://codereview.webrtc.org/2689233003/#ps20001 (title: "Fixing memory leak (forgot delete statement)")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.webrtc.org/...
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: ios32_sim_ios9_dbg on master.tryserver.webrtc (JOB_FAILED, http://build.chromium.org/p/tryserver.webrtc/builders/ios32_sim_ios9_dbg/buil...)
The CQ bit was checked by deadbeef@webrtc.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.webrtc.org/...
CQ is committing da patch. Bot data: {"patchset_id": 20001, "attempt_start_ts": 1487371698558880, "parent_rev": "658c3bb0aba00142284bd464d1e2d693e53f931e", "commit_rev": "a5a472927bb209a053b2648d1f0b006f4c8c30ac"}
Message was sent while issue was closed.
Description was changed from ========== Use std::unique_ptr instead of rtc::scoped_refptr in AsyncInvoker. The AsyncClosures only ever have one thing referencing them, so they should be using std::unique_ptr to manage ownership. Maybe this code was written before std::unique_ptr was available. BUG=None ========== to ========== Use std::unique_ptr instead of rtc::scoped_refptr in AsyncInvoker. The AsyncClosures only ever have one thing referencing them, so they should be using std::unique_ptr to manage ownership. Maybe this code was written before std::unique_ptr was available. BUG=None Review-Url: https://codereview.webrtc.org/2689233003 Cr-Commit-Position: refs/heads/master@{#16680} Committed: https://chromium.googlesource.com/external/webrtc/+/a5a472927bb209a053b2648d1... ==========
Message was sent while issue was closed.
Committed patchset #2 (id:20001) as https://chromium.googlesource.com/external/webrtc/+/a5a472927bb209a053b2648d1...
Message was sent while issue was closed.
A revert of this CL (patchset #2 id:20001) has been created in https://codereview.webrtc.org/2703613006/ by deadbeef@webrtc.org. The reason for reverting is: The change to messagequeue.h isn't backwards compatible. Will reland after making it backwards compatible..
Message was sent while issue was closed.
Description was changed from ========== Use std::unique_ptr instead of rtc::scoped_refptr in AsyncInvoker. The AsyncClosures only ever have one thing referencing them, so they should be using std::unique_ptr to manage ownership. Maybe this code was written before std::unique_ptr was available. BUG=None Review-Url: https://codereview.webrtc.org/2689233003 Cr-Commit-Position: refs/heads/master@{#16680} Committed: https://chromium.googlesource.com/external/webrtc/+/a5a472927bb209a053b2648d1... ========== to ========== Use std::unique_ptr instead of rtc::scoped_refptr in AsyncInvoker. The AsyncClosures only ever have one thing referencing them, so they should be using std::unique_ptr to manage ownership. Maybe this code was written before std::unique_ptr was available. BUG=None Review-Url: https://codereview.webrtc.org/2689233003 Cr-Commit-Position: refs/heads/master@{#16680} Committed: https://chromium.googlesource.com/external/webrtc/+/a5a472927bb209a053b2648d1... ==========
Description was changed from ========== Use std::unique_ptr instead of rtc::scoped_refptr in AsyncInvoker. The AsyncClosures only ever have one thing referencing them, so they should be using std::unique_ptr to manage ownership. Maybe this code was written before std::unique_ptr was available. BUG=None Review-Url: https://codereview.webrtc.org/2689233003 Cr-Commit-Position: refs/heads/master@{#16680} Committed: https://chromium.googlesource.com/external/webrtc/+/a5a472927bb209a053b2648d1... ========== to ========== Relanding: Use std::unique_ptr instead of rtc::scoped_refptr in AsyncInvoker. The AsyncClosures only ever have one thing referencing them, so they should be using std::unique_ptr to manage ownership. Maybe this code was written before std::unique_ptr was available. Originally reverted because it made a change to ScopedMessageData that wasn't backwards compatible, and applications using the rtc::Thread infrastructure may be using it. BUG=None Review-Url: https://codereview.webrtc.org/2689233003 Cr-Commit-Position: refs/heads/master@{#16680} Committed: https://chromium.googlesource.com/external/webrtc/+/a5a472927bb209a053b2648d1... ==========
Description was changed from ========== Relanding: Use std::unique_ptr instead of rtc::scoped_refptr in AsyncInvoker. The AsyncClosures only ever have one thing referencing them, so they should be using std::unique_ptr to manage ownership. Maybe this code was written before std::unique_ptr was available. Originally reverted because it made a change to ScopedMessageData that wasn't backwards compatible, and applications using the rtc::Thread infrastructure may be using it. BUG=None Review-Url: https://codereview.webrtc.org/2689233003 Cr-Commit-Position: refs/heads/master@{#16680} Committed: https://chromium.googlesource.com/external/webrtc/+/a5a472927bb209a053b2648d1... ========== to ========== Relanding: Use std::unique_ptr instead of rtc::scoped_refptr in AsyncInvoker. The AsyncClosures only ever have one thing referencing them, so they should be using std::unique_ptr to manage ownership. Maybe this code was written before std::unique_ptr was available. Originally reverted because it made a change to ScopedMessageData that wasn't backwards compatible, and applications using the rtc::Thread infrastructure may be using it. BUG=None ==========
The CQ bit was checked by deadbeef@webrtc.org
The patchset sent to the CQ was uploaded after l-g-t-m from pthatcher@webrtc.org Link to the patchset: https://codereview.webrtc.org/2689233003/#ps60001 (title: ".")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.webrtc.org/...
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: linux_ubsan on master.tryserver.webrtc (JOB_FAILED, http://build.chromium.org/p/tryserver.webrtc/builders/linux_ubsan/builds/9737)
Description was changed from ========== Relanding: Use std::unique_ptr instead of rtc::scoped_refptr in AsyncInvoker. The AsyncClosures only ever have one thing referencing them, so they should be using std::unique_ptr to manage ownership. Maybe this code was written before std::unique_ptr was available. Originally reverted because it made a change to ScopedMessageData that wasn't backwards compatible, and applications using the rtc::Thread infrastructure may be using it. BUG=None ========== to ========== Relanding: Use std::unique_ptr instead of rtc::scoped_refptr in AsyncInvoker. The AsyncClosures only ever have one thing referencing them, so they should be using std::unique_ptr to manage ownership. Maybe this code was written before std::unique_ptr was available. Originally reverted because it made a change to ScopedMessageData that wasn't backwards compatible, and applications using the rtc::Thread infrastructure may be using it. BUG=None NOTRY=True ==========
The CQ bit was checked by deadbeef@webrtc.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.webrtc.org/...
CQ is committing da patch. Bot data: {"patchset_id": 60001, "attempt_start_ts": 1487383412247170, "parent_rev": "884a7284bd11e46840006e92ea8b5fe52abdde27", "commit_rev": "a8bc1a1f63ca8b899526b5af0203264f8f281772"}
Message was sent while issue was closed.
Description was changed from ========== Relanding: Use std::unique_ptr instead of rtc::scoped_refptr in AsyncInvoker. The AsyncClosures only ever have one thing referencing them, so they should be using std::unique_ptr to manage ownership. Maybe this code was written before std::unique_ptr was available. Originally reverted because it made a change to ScopedMessageData that wasn't backwards compatible, and applications using the rtc::Thread infrastructure may be using it. BUG=None NOTRY=True ========== to ========== Relanding: Use std::unique_ptr instead of rtc::scoped_refptr in AsyncInvoker. The AsyncClosures only ever have one thing referencing them, so they should be using std::unique_ptr to manage ownership. Maybe this code was written before std::unique_ptr was available. Originally reverted because it made a change to ScopedMessageData that wasn't backwards compatible, and applications using the rtc::Thread infrastructure may be using it. BUG=None NOTRY=True Review-Url: https://codereview.webrtc.org/2689233003 Cr-Commit-Position: refs/heads/master@{#16684} Committed: https://chromium.googlesource.com/external/webrtc/+/a8bc1a1f63ca8b899526b5af0... ==========
Message was sent while issue was closed.
Committed patchset #4 (id:60001) as https://chromium.googlesource.com/external/webrtc/+/a8bc1a1f63ca8b899526b5af0... |