Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(26)

Unified Diff: Source/wtf/ThreadingWin.cpp

Issue 415083002: [oilpan]: fix deadlock when leaving a safepoint and sweeping. (Closed) Base URL: svn://svn.chromium.org/blink/trunk
Patch Set: review feedback Created 6 years, 5 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « Source/wtf/ThreadingPthreads.cpp ('k') | no next file » | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: Source/wtf/ThreadingWin.cpp
diff --git a/Source/wtf/ThreadingWin.cpp b/Source/wtf/ThreadingWin.cpp
index 928c0b4c10ab5deb35e86498b39ce6c46eeb6a9a..c133b46982598eea4d1fcf30dbc5b3b5bb67b969 100644
--- a/Source/wtf/ThreadingWin.cpp
+++ b/Source/wtf/ThreadingWin.cpp
@@ -264,23 +264,30 @@ ThreadIdentifier currentThread()
return static_cast<ThreadIdentifier>(GetCurrentThreadId());
}
-Mutex::Mutex()
+MutexBase::MutexBase(bool recursive)
{
m_mutex.m_recursionCount = 0;
InitializeCriticalSection(&m_mutex.m_internalMutex);
}
-Mutex::~Mutex()
+MutexBase::~MutexBase()
{
DeleteCriticalSection(&m_mutex.m_internalMutex);
}
-void Mutex::lock()
+void MutexBase::lock()
{
EnterCriticalSection(&m_mutex.m_internalMutex);
++m_mutex.m_recursionCount;
}
+void MutexBase::unlock()
+{
+ ASSERT(m_mutex.m_recursionCount);
+ --m_mutex.m_recursionCount;
+ LeaveCriticalSection(&m_mutex.m_internalMutex);
+}
+
bool Mutex::tryLock()
{
// This method is modeled after the behavior of pthread_mutex_trylock,
@@ -292,14 +299,16 @@ bool Mutex::tryLock()
DWORD result = TryEnterCriticalSection(&m_mutex.m_internalMutex);
if (result != 0) { // We got the lock
- // If this thread already had the lock, we must unlock and
- // return false so that we mimic the behavior of POSIX's
- // pthread_mutex_trylock:
+ // If this thread already had the lock, we must unlock and return
+ // false since this is a non-recursive mutex. This is to mimic the
+ // behavior of POSIX's pthread_mutex_trylock. We don't do this
+ // check in the lock method (presumably due to performance?). This
+ // means lock() will succeed even if the current thread has already
+ // entered the critical section.
if (m_mutex.m_recursionCount > 0) {
LeaveCriticalSection(&m_mutex.m_internalMutex);
return false;
}
-
++m_mutex.m_recursionCount;
return true;
}
@@ -307,11 +316,16 @@ bool Mutex::tryLock()
return false;
}
-void Mutex::unlock()
+bool RecursiveMutex::tryLock()
{
- ASSERT(m_mutex.m_recursionCount);
- --m_mutex.m_recursionCount;
- LeaveCriticalSection(&m_mutex.m_internalMutex);
+ // CRITICAL_SECTION is recursive/reentrant so TryEnterCriticalSection will
+ // succeed if the current thread is already in the critical section.
+ DWORD result = TryEnterCriticalSection(&m_mutex.m_internalMutex);
+ if (result == 0) { // We didn't get the lock.
+ return false;
+ }
+ ++m_mutex.m_recursionCount;
+ return true;
}
bool PlatformCondition::timedWait(PlatformMutex& mutex, DWORD durationMilliseconds)
@@ -444,12 +458,12 @@ ThreadCondition::~ThreadCondition()
CloseHandle(m_condition.m_unblockLock);
}
-void ThreadCondition::wait(Mutex& mutex)
+void ThreadCondition::wait(MutexBase& mutex)
{
m_condition.timedWait(mutex.impl(), INFINITE);
}
-bool ThreadCondition::timedWait(Mutex& mutex, double absoluteTime)
+bool ThreadCondition::timedWait(MutexBase& mutex, double absoluteTime)
{
DWORD interval = absoluteTimeToWaitTimeoutInterval(absoluteTime);
« no previous file with comments | « Source/wtf/ThreadingPthreads.cpp ('k') | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698