[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 252659] deadlock due to ForegroundLock
From:       David Nolden <david.nolden.kde () art-master ! de>
Date:       2010-12-01 13:02:36
Message-ID: 20101201130236.A3BE57663D () immanuel ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=252659





--- Comment #7 from David Nolden <david nolden kde art-master de>  2010-12-01 14:02:32 ---
I think the code "with workaround" is better than without, so it can stay. We
track the recursion anyway, so the QMutex doesn't need to do it.

Regarding QAtomic: "holderThread" and "recursion" are protected by the
internalMutex, so they don't need to be atomic. They can only be written by one
thread at a time.

Please look at the code of lockMutexInternal, tryLockMutexInternal, and
unlockMutexInternal to find some mistakes, maybe I've missed something.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]