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

List:       kdevelop-bugs
Subject:    [Bug 228859] UIBlockTester::lockup: deadlock while editing source code
From:       Nicolai Haehnle <prefect_ () gmx ! net>
Date:       2010-02-28 8:48:54
Message-ID: 20100228084854.8FEC6355AE () immanuel ! kde ! org
[Download RAW message or body]

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





--- Comment #3 from Nicolai Haehnle <prefect_ gmx net>  2010-02-28 09:48:53 ---
Curiously, I just continued the KDevelop instance from which I collected the
backtraces, and after a while I did get some output of the form:

kdevelop(11024)/kdevelop (cpp support) UIBlockTester::lockup: ui is blocking
kdevelop(11024)/kdevplatform (language)
KDevelop::DUChainPrivate::doMoreCleanup: starting cleanup
kdevelop(11024)/kdevelop (cpp support) UIBlockTester::lockup: ui is blocking
kdevelop(11024)/kdevelop (cpp support) UIBlockTester::lockup: ui is blocking
kdevelop(11024)/kdevelop (cpp support) UIBlockTester::lockup: ui is blocking
kdevelop(11024)/kdevplatform (language)
KDevelop::DUChainPrivate::doMoreCleanup: milliseconds spent doing cleanup with
locked duchain:  124
kdevelop(11024)/kdevplatform (language)
KDevelop::DUChainPrivate::doMoreCleanup: seconds spent doing cleanup:  1
top-contexts still open: 1103
kdevelop(11024)/kdevelop (cpp support) UIBlockTester::lockup: ui is blocking

It then again continues with the "ui is blocking" and indeed, KDevelop still
hangs.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

_______________________________________________
KDevelop-bugs mailing list
KDevelop-bugs@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-bugs
[prev in list] [next in list] [prev in thread] [next in thread]