This week, in the latest KDE-CVS-Digest read about the many improvements in the development tools. In KDevelop,
work continues on code completion and new code templates.
Quanta gets ktips and finishing polishes.
Kate, Cervisia, KBabel and Umbrello continue to get better.
Support for new XFree86 features are being implemented.
And nothing like a gathering of developers (report) to
improve the games.
Dot Categories:
Comments
There are no exotic things in my configuration. The panel have only minipager, taskbar, clock and K button. The leak is seen for a long time, certainly since KDE 3.0. I have tried various configuration options before compilation, Slackware`s packages.
kicker's memory usage grows over time.
I either have to restart or kill kicker and let kdeinit start it back up
It takes up 14.4mb on startup, it was taking 68mb before I killed it. I don't know why a panel would need to take up so much memory.
14.4 mb on startup isn't bad at all considering how much of that is likely shared. leaks causing it to go to 68mb is bad however. is there any special usage of it that causes this? I've been valgrind'ing kicker for a week now, and I've caught one leak so far, but it caused a loss of ~300k or so for 45 mins time.
I get a HUGE memory leak in kicker in Redhat 9.
It's been one day since I last killed it, and it's using almost a gigabyte!
The only applets I am running is Klipper and Clock
Surely others have noticed this?
[craig@localhost script]$ ps axv | grep kde
1995 ? S 0:00 1799 588 3559 984 0.0 /bin/sh /usr/bin/startkde
2098 ? S 0:00 236 31 25692 7856 0.7 kdeinit: Running...
2101 ? S 0:00 101 31 27400 8264 0.8 kdeinit: dcopserver --nosid
2104 ? S 0:00 325 31 28568 9312 0.9 kdeinit: klauncher
2106 ? S 4:07 800 31 29756 10440 1.0 kdeinit: kded
2127 ? S 0:00 846 31 34288 10092 0.9 kdeinit: knotify
2130 ? S 0:00 735 31 29532 10156 0.9 kdeinit: ksmserver
2131 ? S 0:16 1147 31 30576 12096 1.1 kdeinit: kwin -session 117f000001000105549695300000045610000_1059381616_912699
2133 ? S 0:33 1470 31 31220 10120 0.9 kdeinit: kdesktop
2135 ? S 1:53 1488 31 2685844 563264 54.5 kdeinit: kicker
2136 ? S 0:00 130 31 26060 8660 0.8 kdeinit: kio_file file /tmp/ksocket-craig/klauncherg3IRkc.slave-socket /tmp/ksocket-craig/kdesktopN8xY1a.slave-socket
2143 ? S 0:00 848 31 30192 10388 1.0 kdeinit: kwrited
2149 ? S 0:04 729 31 29620 10136 0.9 kdeinit: kaccess -session 117f000001000105551438800000045610044_1059381616_906129
2153 ? S 13:08 1503 31 34500 15184 1.4 kdeinit: konsole
19955 ? S 0:18 2374 31 37200 15088 1.4 kdeinit: konqueror --silent
2214 pts/6 S 0:00 164 70 3521 648 0.0 grep kde
[craig@localhost script]$ free
total used free shared buffers cached
Mem: 1032680 1019848 12832 0 135580 130616
-/+ buffers/cache: 753652 279028
Swap: 1028120 291184 736936
[craig@localhost script]$ kill 2135
[craig@localhost script]$ free
total used free shared buffers cached
Mem: 1032680 439760 592920 0 135504 134492
-/+ buffers/cache: 169764 862916
Swap: 1028120 52520 975600
There is indeed a memory leak in kicker. On my RH 9 system, if it is allowed to get out of hand, it can bog my whole system down with swapping, forcing a reboot (!)
The leak seems to be a function of how much you use the launcher. Killing kicker and restarting it effects a cleanup.
I created a simple script to kill -s SIGINT the kicker process and run up kicker again immediately. It works.
Try
kill -s SIGINT `ps --no-headers --format=%p -C kicker`
kicker
Put this in cron to run nightly, or even hourly, depending on requirements.
Of course this assumes you have KDE up constantly.
PS. The above is just a hack to demonstrate that killing and relaunching kicker frees up the memory kicker was holding. I don't suggest you try and put that script into a cron job as is! Also note: allowing multiple kickers to run at the same time is definitely not recommended. :|
well im using kicker on SuSe FActory and when i start kde it uses all cpu all i do is send signall SIGSTOP and its ok no killking.
Is there a simple way to find out which branches exist in the CVS, e.g. KDE_3_1_RELEASE, HEAD, etc.? I can't find a list anywhere.
Go to say http://webcvs.kde.org/cgi-bin/cvsweb.cgi/kdelibs/ and look on the bottom of the page. There is a dropdown list of the branches.
If you do a cvs log (check the syntax) the log file lists the branches and revision numbers.
Derek
You can go to http://webcvs.kde.org. Then select a module and have a look at the combo box at the end of the page.
...until everybody is happy and people stop complaining about it. See also the comments at:
http://osnews.com/comment.php?news_id=2841
I'll quote a few things:
[quote]
I have a hard time trusting the aesthetic sense of
some linux enthusiasts. These are the same people who
were oohing and aahingsaying over Gnome desktops
back whey they were butt ugly.
And they sure as hell weren't nicer looking than
W95. despite this being an article of faith among many
Windows looks has always been the most trivial of my
concerns with Microsoft.
[/quote]
-- and --
[quote]
I've tried KDE on my Pentium 2 266, 96 Meg RAM (and a 1 yr old 20 gig hard drive) and it's painfully slow - starting kde takes forever, and launching relatively lightweight apps takes at least 15 seconds. Basically it's too slow to be useable. However i've found gnome 2 to be significantly faster - both when starting up, and when launching apps. I'm not going to have a go at KDE for requiring a reasonably fast machine to rnu comfortably, it was never meant to be a lightweight desktop, i just won't use it on machines any slower than a pentium 3.
[/quote]
-- and --
[quote]
By Eugenia (IP: ---.client.attbi.com) - Posted on 2003-02-18 00:01:09 Konqueror is the most buggy part of KDE. Maybe because it is the most complex one. Point is, it does not always work as expected, in fact it has right-click menus for items that don't make sense to have specific options, and in general is *buggy*, crashy and bloated.
As for KDE overall, while we seen it adding a lot of new features lately, it REMAINS unpolished, bloated and without a direction: It includes system utilities for some things, and not for others. It includes certain user-level applications, but not everything. KDE has an identity crisis and leaving a few preferences to the distribution while handling others through KDE is just weird. And inconsistent.
More over, the KDE 3.1 Kontrol Center is the Center Of All Laughs. I have never seen a more bloated preference panel in my life, having more about 30-40 leaves in the tree excluding the number of tabs for each leaf/option! Soon you forget where is where. It is just unusable. Terrible.
One year ago I had Gnome out of the horizon and considered KDE the only leading Linux DE. One year later, and *because* of the Red Hat involvement on Gnome 2, I actually tend to see Gnome2 having a better face today. Gnome2 still sucks, but for a DE, is simpler and more predictable than KDE. KDE tries to do everything, adds apps to the mix and instead of focus to the usability and how to clean up their chaotic existance, they add more to the mix. A shame.
[/quote]
Looks like there's still a lot of work left to be done. People still don't take Linux or KDE seriously. There's still waaaay too much critism about KDE and Linux.
*yawn*
Ask yourself whether all those comments stopped people from using Windows.
As for me I'm using KDE on a AMD K6-2 300mHz with 224MB RAM. Program startup is slower but everything else is faster than under Windows on the same computer (can't play Ogg and Divx under Windows without heavy skips, stuff like that). A desktop's look is the biggest non-issue I've ever heard about: if you don't like it, change it. Tastes are different in different times and between different persons so it's the worst part to rate a desktop after. Usability is the only valid concern, but it's also the part where both Gnome and KDE sped up a lot as of late.
Criticism is fine as long as it is constructive. Sadly many people seem to ignore this and prefer badmouthing to contributing. And with community projects like KDE contributing does make a difference.
3.1 is dramatically faster and more finished than any previous release. To emulate an earlier version of kde, I have to run an emerge -u world in the background. Then it feels just like 3.0.
Seriously. The pace of development is so quick in the linux desktop (both kde and gnome) that any opinion is out of date quickly.
When I hear a complaint, the first question is "what distribution and version".
More importantly, I have yet to request permission to use any of the linux desktops. Seems to me one has to with XP, or it doesn't work very long.
Derek
Well, I've used Windows before at home and in my company.
First, I switched from Windows in my company, a few weeks later
at home. I didn't know anything about Linux or KDE so I jumped
in at the deep end. I was never interested in Linux and a big
sceptic. But at work and at home my Windows XP crashed often even
after installing on a fresh formatted HD. The task bar
vanished, I got a virus just by *viewing* an email and I thought:
"OK, it's bad, but computers are like this". In my company we
used Linux only on servers. Nobody had any experience of using
Linux as a regular desktop OS. My colleagues switched our
servers from Windows to Linux after lots of strange crashes, hangs
and other problems with our mail server. One day, I just started Windows
and was editing a text in NotePad(!) all of a sudden my computer rebooted.
That was the last time I saw Windows on the screen of my computer.
I took our SuSE 8.1 CD and installed it not knowing if I might regret
this step. After 20 minutes KDE was installed. To my amazement all
hardware was detected correctly. I needed some time to get used to all
the new concepts like different Users, no EXE files, and I needed some
time to find out which application is best for my purposes.
But what I really noticed right from the start is the speed and stability.
I can run my computer for days, opening and closing applications, installing
new applications without ever having to restart my computer. And my computer
(1 GhZ, 128 MB RAM) runs so fast I never thought it could be possible.
I never hear my hard disk working for minutes when I start an application.
To all sceptics: Try this under Windows and Linux.
Copy a file over the network with Explorer/Konqueror.
While it is copying start Word/KWord. While Word is starting and
the files are copying, start Notepad/KWrite and start writing some
text. In Linux/KDE all this is no problem. In Windows, you can be
lucky if Word starts after minutes and heavy disk activity. In the
mean time your computer becomes dead slow. So I found out why
Linux applications do not have a splash screen. They do not need
one: You can run the application and keep on working until it is started.
So if you are not into computer Games which are mostly for Windows only:
Yes KDE is ready for the desktop and I wonder why people keep saying
its to slow? Well, I wanted to point out here that I experienced
the opposite to be the case.
> One day, I just started Windows
and was editing a text in NotePad(!) all of a sudden my computer rebooted.
Things like that usually point to Hardware-Problems, ie. defect or incompatible hardware. Of course, it might also be due to bad drivers, configuring some hardware in ways, that they do conflict with each others.
Yet, it seems Linux is even in this regard more "stable" than Windows.
Regards,
Harald Henkel
Well, I can only say:
I installed Windows with autodetected hardware & drivers.
I installed Linux with autodetected hardware & drivers.
Windows crashes. Linux does not.
It's as simple as that.
Hardware problems? I doubt it!