If this is your first visit, be sure to
check out the FAQ. You will have to register
before you can post. To start viewing messages,
select the forum that you want to visit from the selection below.
Please do not use the CODE tag when pasting content that contains formatting (colored, bold, underline, italic, etc).
The CODE tag displays all content as plain text, including the formatting tags, making it difficult to read.
Announcement
Collapse
No announcement yet.
Kubuntu 15.04 Beta 2 unusable after a short period of time
I didn't start having a problem until I rebooted my computer sometime after the update. Have you restarted (or logged-out and back in I guess would have the same effect) since kubuntu-notification-helper was installed?
If so, then I guess the next question is why some have the problem and others do not.
Rebooted out of curiosity about 15 minutes ago. So far no runaway processes. kded5 is at 44MB.
Seems to be the problem. Looks like a recursive call in the kubuntu-notification-helper package.
For me, the desktop would run fine for a few minutes, and I could watch the kded5 process slowly eating all my ram (1.5GB... 2.0GB... 3.0GB... etc.) until my system was unusable.
I have temporarily removed the kubuntu-notification-helper package and it seems to have solved the issue.
For curiosity sake. I re-installed the kubuntu-notification-helper.
Logged out, then logged back in.
The only thing I opened was System Monitor (CTRL + ESC).
After about 5 minutes kded5 runs away with my RAM again.
I went into the console and purged the package again. Then decided maybe I should try to get some sort of meaningful information out of System Monitor: http://pastebin.com/wEj21MmZ
Curioser and curioser. Here, after well over an hour since rebooting:
Process 7704 - kded5
Summary
The process kded5 (with pid 7704) is using approximately 87.5 MB of memory.
It is using 46.6 MB privately, and a further 108.9 MB that is, or could be, shared with other programs.
Dividing up the shared memory between all the processes sharing that memory we get a reduced shared memory usage of 40.9 MB. Adding that to the private usage, we get the above mentioned total memory footprint of 87.5 MB.
The process kded5 (with pid 1446) is using approximately 106.4 MB of memory.
It is using 60.1 MB privately, and a further 130.8 MB that is, or could be, shared with other programs.
Dividing up the shared memory between all the processes sharing that memory we get a reduced shared memory usage of 46.3 MB. Adding that to the private usage, we get the above mentioned total memory footprint of 106.4 MB.
I'm affected by this issue as well. I tried to find out what is happening by running htop in konsole and it seems that kded5 is running the system out of resources and effectively making it unresponsive.
I experienced the very slow cursor movement, but today the cursor is OK but the clock stops and I cannot launch anything for a period. Then after a while it springs back to life. I did see kded5 using 100% CPU.
I left my system run for over an hour and when I came back the Swap file had 528 MB used?
I am beginning to worry about the state of Vivid by the release date with all these serious problems arising. At least Muon can now be used as the menu bar is back! There are still a lot of other GUI aspects that need polishing up for Vivid to be acceptable.
Comment