DescriptionEnsureOpenSSLInit before calling into WebRTC.
BoringSSL may currently only be initialized by one piece of code, so full
initialization must happen in Chromium code, rather than WebRTC.
Historically, this was because the locking callbacks needed to be configured.
This is gone, but EnsureOpenSSLInit still configures NEON support on Android
and detects a CPU with known broken NEON support. Until that's moved to inside
the library (https://crbug.com/542879), Chromium must initialize some of the
stack ourselves.
BUG=556462
Committed: https://crrev.com/f044335430bdadadc8c31653a38551eda48994c6
Cr-Commit-Position: refs/heads/master@{#360466}
Patch Set 1 #
Messages
Total messages: 9 (3 generated)
|