diff options
| author | ripp <ripp@yandex-team.ru> | 2015-02-26 00:07:49 -0800 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2015-02-26 08:08:32 +0000 |
| commit | e1d5ac1d7c0a594f0c218c7031095ad684cc56df (patch) | |
| tree | cffbb157198714ead79d278ccb53a61df0e4e28e /content/child/webcrypto/generate_key_result.h | |
| parent | 233c55e44b76aa0419772d90344a188f758848b6 (diff) | |
| download | chromium_src-e1d5ac1d7c0a594f0c218c7031095ad684cc56df.zip chromium_src-e1d5ac1d7c0a594f0c218c7031095ad684cc56df.tar.gz chromium_src-e1d5ac1d7c0a594f0c218c7031095ad684cc56df.tar.bz2 | |
Removed unnecessary potential locking
Function isInitialized, unlike calls ensureinitialized should not block
the thread, but it will if initialization is in progress at this moment.
It is not necessery to synchronize the sInitialized flag in
isInitialized function. It is enough that flag have a primitive type and
has a volatile qualifier.
R=nyquist@chromium.org, rmcilroy@chromium.org
TEST=It is rather hard to test. We've found ~300ms stuck on UI thread,
on calling LibraryLoader.isInitialized from ContentApplication.onCreate
with profiler
Review URL: https://codereview.chromium.org/925513002
Cr-Commit-Position: refs/heads/master@{#318208}
Diffstat (limited to 'content/child/webcrypto/generate_key_result.h')
0 files changed, 0 insertions, 0 deletions