UIBlockTester::lockup: ui is blocking

David Nolden zwabel at googlemail.com
Mon Nov 9 07:44:44 UTC 2009


Am Montag 09 November 2009 00:20:17 schrieb Andreas Pakulat:
> On 08.11.09 23:11:51, David Nolden wrote:
> > Am Sonntag 08 November 2009 21:28:01 schrieb Esben Mose Hansen:
> > > Hi,
> > >
> > > while working with the new fancy controlflowgraph I seem to be getting
> > > a lot of these. Could it be the controlflowgraph's fault? What does it
> > > mean?
> >
> > Yes it probably is the control-flow graphs fault. It means that the
> > main-loop was not entered for X milliseconds (where X is by default 300 I
> > think). That again means that the GUI is blocked, which sucks. It has to
> > be prevented by moving very intensive work (especially regarding the
> > duchain) into a background thread, which I think the control-flow graph
> > plugin doesn't do.
> 
> Does this also "fire" when some non-language-related stuff is going on in
> the GUI? I'm pretty sure that drawing the graph via graphviz will be
> blocking and cannot be changed, so that would explain the message.
> 
> Andreas
> 
Yep, it fires on any delay.




More information about the KDevelop-devel mailing list