New issue
Advanced search Search tips
Starred by 1 user

Issue metadata

Status: Verified
Closed: Apr 2016
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Feature

Sign in to add a comment

Issue 592752: Investigate and Move to Windows SRWLocks for base::Lock

Reported by, Mar 7 2016 Project Member

Issue description

Slim Reader/Writer Locks (SRWLock)

Now that we're on Win7+, we can investigate and move towards SRWLocks. They're pointer sizes and generally faster than critsecs under exclusive mode.

Comment 1 by, Mar 7 2016

Labels: -Type-Bug Type-Feature

Comment 2 by, Apr 5 2016

Components: Internals>PlatformIntegration

Comment 3 by, Apr 5 2016

Tightloop Tests on a Powerful Machine

  for (unsigned int i = 0; i < 10000000; ++i) {


  for (unsigned int i = 0; i < 10000000; i++) {

The SRWLock version for release builds is around 20-30 ms faster. 
On debug builds, SRWLock is around 40-50 ms faster.

Comment 4 by, Apr 5 2016

Status: Started (was: Available)

Comment 5 by, Apr 11 2016

Project Member

Comment 6 by, Apr 12 2016

Status: Verified (was: Started)

Comment 7 by, Jun 1 2017

Project Member
The following revision refers to this bug:

commit 8ce8b7f02264873346f8a6ca0be5b6492dd4e7c4
Author: Loo Rong Jie <>
Date: Thu Jun 01 12:18:44 2017

[base] Migrate Mutex from CRITICAL_SECTION to SRWLOCK

SRWLOCK is a faster and lightweight alternative of CRITICAL_SECTION for
non-recursive use case.

Bug:  chromium:592752 
Change-Id: Ie97cd9cee2d50a95f316b41c30e953f586b06c99
Reviewed-by: Jochen Eisinger <>
Commit-Queue: Loo Rong Jie <>
Cr-Commit-Position: refs/heads/master@{#45658}

Sign in to add a comment