e35004dffb
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}
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.
Development
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.
More info
- Official web site: http://www.webrtc.org
- Master source code repo: https://webrtc.googlesource.com/src
- Samples and reference apps: https://github.com/webrtc
- Mailing list: http://groups.google.com/group/discuss-webrtc
- Continuous build: http://build.chromium.org/p/client.webrtc
- Coding style guide
- Code of conduct