From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Plasmashell consuming huge amounts of memory.
Date: Mon, 16 Oct 2017 21:58:11 -0500 [thread overview]
Message-ID: <28e361f8-5043-9b6d-d754-3317fe9b21c9@gmail.com> (raw)
In-Reply-To: <20171017013237.GJ1957@ca.inter.net>
Philip Webb wrote:
> 171016 Dale wrote:
>>> I did a upgrade recently
>> and after that, plasmashell is consuming a huge amount of memory.
>> I noticed it at one point and it was taking about 8 GB .
> FYI I don't see this :
>
> root:527 ~> eix plasma-work
> [I] kde-plasma/plasma-workspace
> Available versions: (5) 5.10.5-r1^t ~5.11.0^t
> Installed versions: 5.10.5-r1(5)^t([2017-09-19 22:08:06]) (handbook -appstream -calendar -debug -geolocation -gps -prison -qalculate -semantic-desktop -test)
>
> root:528 ~> free
> total used free shared buff/cache available
> Mem: 7906 1180 5271 139 1454 6041
> Swap: 8191 0 8191
>
> root:529 ~> uptime
> 21:28:07 up 1 day, 20:43, load average: 0.01, 0.05, 0.02
>
We have slightly different USE flags. Here's mine:
[ebuild R ~] kde-plasma/plasma-workspace-5.11.0:5::gentoo
USE="calendar handbook -appstream -debug -geolocation -gps -prison
-qalculate -semantic-desktop -systemd {-test}" 0 KiB
I notice systemd is missing in yours, not on or off just not there at
all. I'm not sure exactly what calendar does but I do use the one in
the little panel thingy. Not sure if it is the same one or not.
This doesn't seem to affect everyone but it seems to affect some of us.
It seems you are lucky and I'm hoping after going to a new .kde4 that
I'll have the same luck. I've had times before where this helped. Just
something in a config somewhere that causes problems. Besides, I run a
somewhat weird setup anyway. I'm old, that's my excuse and I'm sticking
with it. LOL
Interesting info. Makes one wonder.
Dale
:-) :-)
next prev parent reply other threads:[~2017-10-17 2:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 23:28 [gentoo-user] Plasmashell consuming huge amounts of memory Dale
2017-10-12 0:08 ` P Levine
2017-10-12 3:09 ` Dale
2017-10-12 3:36 ` P Levine
2017-10-12 4:40 ` Dale
2017-10-12 6:18 ` P Levine
2017-10-12 6:46 ` Dale
2017-10-17 0:41 ` Dale
2017-10-17 0:58 ` P Levine
2017-10-17 3:03 ` Dale
2017-10-17 8:39 ` Peter Humphrey
2017-10-17 8:50 ` Dale
2017-10-17 1:32 ` Philip Webb
2017-10-17 2:58 ` Dale [this message]
2017-10-17 8:23 ` Dale
2017-10-26 19:30 ` Dale
2017-10-28 18:49 ` Dale
2017-10-28 22:03 ` P Levine
2017-10-28 22:35 ` Dale
2017-10-28 22:44 ` R0b0t1
2017-10-28 22:59 ` Dale
2017-10-28 23:59 ` P Levine
2017-10-29 1:51 ` Dale
2017-10-29 3:08 ` Dale
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=28e361f8-5043-9b6d-d754-3317fe9b21c9@gmail.com \
--to=rdalek1967@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox