Remove TryAcquireSRWLock from Chromium sandbox even though it's unused

Author: K4sum1

ipc/chromium/src/base/lock_impl_win.cc

@@ -13,8 +13,6 @@ LockImpl::LockImpl() : native_handle_(SRWLOCK_INIT) {}
 
 LockImpl::~LockImpl() = default;
 
-bool LockImpl::Try() { return !!::TryAcquireSRWLockExclusive(&native_handle_); }
-
 void LockImpl::Lock() { ::AcquireSRWLockExclusive(&native_handle_); }
 
 void LockImpl::Unlock() { ::ReleaseSRWLockExclusive(&native_handle_); }

security/sandbox/chromium/base/synchronization/lock_impl_win.cc

@@ -15,11 +15,6 @@ LockImpl::LockImpl() : native_handle_(SRWLOCK_INIT) {}
 
 LockImpl::~LockImpl() = default;
 
-bool LockImpl::Try() {
-  return !!::TryAcquireSRWLockExclusive(
-      reinterpret_cast<PSRWLOCK>(&native_handle_));
-}
-
 void LockImpl::Lock() {
   // The ScopedLockAcquireActivity below is relatively expensive and so its
   // actions can become significant due to the very large number of locks
@@ -28,10 +23,6 @@ void LockImpl::Lock() {
   // (tracked) blocking call if that fails. Since "try" itself is a system
   // call, and thus also somewhat expensive, don't bother with it unless
   // tracking is actually enabled.
-  if (base::debug::GlobalActivityTracker::IsEnabled())
-    if (Try())
-      return;
-
   base::debug::ScopedLockAcquireActivity lock_activity(this);
   ::AcquireSRWLockExclusive(reinterpret_cast<PSRWLOCK>(&native_handle_));
 }