commit | cf84607875d5dd13e33dddf33cf457d9a5f25e2c | [log] [tgz] |
---|---|---|
author | Tommi <tommi@webrtc.org> | Sun May 17 12:51:10 2020 |
committer | Commit Bot <commit-bot@chromium.org> | Sun May 17 17:22:01 2020 |
tree | 3958e3bf773a94e6d0574b53472c1b41bf33f8b9 | |
parent | 04c94ad4916e121368ee20867eaa333e14222cd2 [diff] |
Reland "Use Windows 10 thread naming API" This reverts commit d0d55515c4b88a07446bc66a5c183f50ee896282. Reason for revert: Relanding with workaround. Original change's description: > Revert "Use Windows 10 thread naming API" > > This reverts commit e35004dffb42dd96b8cf37b33c9a3af4a5fd376c. > > Reason for revert: Reverting while downstream issue is resolved. > > Original change's description: > > Use Windows 10 thread naming API > > > > While profiling video chat in Chrome I noticed that some of the webrtc > > threads were not named. This change adds conditional use of the thread > > naming APIs. These thread names work even if you attach a debugger after > > the thread is named, and they show up in ETW traces, for easier > > profiling. > > > > The sctp_create_thread_adapter threads are still not named but since > > those are in C files they would require a C++-with-extern-C interface > > to fix, so I'm leaving them for now. > > > > Bug: webrtc:10745 > > Change-Id: I68f6aa780e2417ce706764d69e5b64cc48aba333 > > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/175280 > > Commit-Queue: Tommi <tommi@webrtc.org> > > Reviewed-by: Tommi <tommi@webrtc.org> > > Reviewed-by: Karl Wiberg <kwiberg@webrtc.org> > > Cr-Commit-Position: refs/heads/master@{#31285} > > TBR=kwiberg@webrtc.org,tommi@webrtc.org,brucedawson@chromium.org > > Change-Id: Icf877afbd82918ebe0c42a93b8a763cdab9a73ce > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: webrtc:10745 > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/175347 > Reviewed-by: Tommi <tommi@webrtc.org> > Commit-Queue: Tommi <tommi@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#31289} TBR=kwiberg@webrtc.org,tommi@webrtc.org,brucedawson@chromium.org Bug: webrtc:10745 Change-Id: I51ee413fd8a0ff62f6b8b2a11f546b2a70168842 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/175349 Reviewed-by: Tommi <tommi@webrtc.org> Commit-Queue: Tommi <tommi@webrtc.org> Cr-Commit-Position: refs/heads/master@{#31292}
WebRTC is a free, open software project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The WebRTC components have been optimized to best serve this purpose.
Our mission: To enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols.
The WebRTC initiative is a project supported by Google, Mozilla and Opera, amongst others.
See here for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.