From kdevelop-devel  Wed Mar 24 08:41:57 2004
From: Jens Dagerbo <jens.dagerbo () swipnet ! se>
Date: Wed, 24 Mar 2004 08:41:57 +0000
To: kdevelop-devel
Subject: Re: CVS HEAD problems
Message-Id: <200403240941.58001.jens.dagerbo () swipnet ! se>
X-MARC-Message: https://marc.info/?l=kdevelop-devel&m=108011787727605


On Wednesday 24 March 2004 09:35, Andras Mantia wrote:
> Jens Dagerbo wrote:
> > On Wednesday 24 March 2004 03:23, Jens Dagerbo wrote:
> >> And.. it doesn't happen with the QEditor part, only with katepart.
> >
> > I tracked it down to this commit:
> >
> > M +58 -42    katebookmarks.cpp   1.32
> >
> > Anders,
> > I'm guessing the reason your commit messes up KDevelop but not Kate is
> > that you have delayed creation of the view in Kate but we don't, so when
> > KDevelop starts up and loads a set of editors, they will each start
> > looping and waiting for focus.
> >
> > Background:
> > Kate bug: http://bugs.kde.org/show_bug.cgi?id=77247
> > KDevelop Thread: http://lists.kde.org/?t=108004213800001&r=1&w=2
>
> After I wrote the mail about KDevelop using 100% CPU, I found that Quanta
> uses 100% CPU as well in some cases, without doing anything with an empty
> opened file. I tried to find the reason and my conclusion also was that
> kdelibs has been broken in the last days. Today I wanted to try with an
> older kdelibs and compare the differences, but I see that you've already
> found the cause! I will also try if reverting that commit helps us or not.
> Anyway, that's a big problem for katepart users.
>
> See also my mail on KDE Optimize mailing list ("100% CPU usage in Quanta").
>
> Andras

Just update. Anders fixed his fix. :)

jd


_______________________________________________
Kdevelop-devel mailing list
Kdevelop-devel@barney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel