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

List:       kde-bugs-dist
Subject:    [Bug 252659] deadlock due to ForegroundLock
From:       Milian Wolff <mail () milianw ! de>
Date:       2010-12-14 18:41:02
Message-ID: 20101214184102.8295C781B0 () immanuel ! kde ! org
[Download RAW message or body]

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





--- Comment #20 from Milian Wolff <mail milianw de>  2010-12-14 19:40:32 ---
Created an attachment (id=54555)
 --> (http://bugs.kde.org/attachment.cgi?id=54555)
irc log from 14th of december 2010 with till, thiago and others about the
foreground lock

some more information from a IRC discussion. It showed a few things:

a) the test case was not minimal and did not use the custom QApplication with
the notify overload, I've since reduced it quite much, fixed the issues, and
put the code up on git: git@git.kde.org:scratch/mwolff/foregroundlock-test
this is a standalone and minimal version exhibiting the deadlock.

b) it still looks like a Qt internal issue, as described by Till

c) the code for nested eventloops in relock is very bad according to Thiago,
see attachement

d) we should in the future spent time to use a proper design, e.g. the memento
pattern, to make this foreground lock obsolete. It is a hack according to
Thiago, Till and others. People like Roberto Raggi, Christoph Cullman and
others also urged us to use this.

e) While being a hack, it is technically "correct" according to Till and should
work

f) maybe more that I forgot to mention...

-- 
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]