Re: [kde-linux] Konqueror and Dolphin using 100% CPU
- Date: Thu, 08 Mar 2012 01:07:41 -0600
- From: Dale <rdalek1967@xxxxxxxxx>
- Subject: Re: [kde-linux] Konqueror and Dolphin using 100% CPU
> Duncan posted on Thu, 08 Mar 2012 04:17:35 +0000 as excerpted:
>> Dale posted on Wed, 07 Mar 2012 18:24:08 -0600 as excerpted:
>>> Remember my post a while back that said just because I don't respond
>>> doesn't mean I'm not trying? Well, I installed and been testing
>>> krusader for the past few days. I didn't want to post to quick because
>>> I jinxed it last time when I thought Konqueror was working. Anyway, I
>>> switched it so that everything opens with Krusader and so far,
>>> everything works fine. It's not like Konqueror which is what I am used
>>> to but it doesn't slam my CPU either.
> FWIW, I see a couple bugfixes in the published 4.8.1 changelog that might
> be related to dolphin and konqueror eating 100% cpu.
> One of them mentions a possible endless loop being triggered when resizing
> a dolphin window smaller, kde bug #289238. Another simply mentions
> "problems" with an integer overflow in sort-by-size mode, #293068.
> Presumably that'd be for really large files.
> There's several crasher bugs fixed too. You weren't crashing, but it's
> possible one or more of them could trigger endless loops in some
> circumstances, too.
> FWIW, I upgraded to 4.8.1 a day or two ago, before the public
> announcement. Seems the tarballs were either available before the
> announcement, or gentoo/kde took a cue from arch and mirrored them early,
> before the public announcement. (KDE normally makes tarballs available to
> the distro packagers nearly a week in advance, so they can test and
> hopefully have packages ready by the announcement.) I had been a bit
> jealous of arch users, since their packager apparently was mirroring the
> tarballs before the public announcement, but at least this time, it
> appears either gentoo/kde or kde itself did a pre-announce release as
> Making them available a day or two before the public announcement does
> makes sense, tho, since it'll mean less pressure on the servers in the 48
> hours or so immediately following a release. I don't know what the
> bandwidth usage is like, but spreading it out won't hurt, for sure.
> Anyway, now the announcement is out, so I can see a bit of what I upgraded
> for. =:^)
> The short dot blurb (nothing there really but a place to comment;
> sometimes the comments are interesting to read.
> Announcement (not much of significance there either):
> Changelog (the fixes I mention are listed here; it doesn't list all
> changes, but links the svn/git logs):
I did my updates yesterday. I'll open Konqueror and see if it is fixed.
As I mentioned before, I want it fixed even if I don't use them any more.
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!
Miss the compile output? Hint:
This message is from the kde-linux mailing list.
Account management: https://mail.kde.org/mailman/listinfo/kde-linux.
More info: http://www.kde.org/faq.html.