public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Plasmashell consuming huge amounts of memory.
Date: Tue, 17 Oct 2017 03:23:31 -0500	[thread overview]
Message-ID: <cc3d44e2-9533-6156-1f95-b6a395762686@gmail.com> (raw)
In-Reply-To: <a5c733f8-4dda-07d9-df73-f2652fc6249f@gmail.com>

Dale wrote:
> Dale wrote:
>> Howdy,
>>
>> 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
>> 8GBs.  I killed it and restarted but it seems to keep happening after a
>> few hours.  After I took a nap, I nudged the monitor back to the on
>> state only to notice it had eaten so much memory that the system killed
>> plasmashell and I had to restart it then.  It also made other programs
>> go to swap since it was full as well.  Glad the system dealt with it
>> instead of just crashing the whole thing. 
>>
>> After I restart it, it goes back to normal, a few hundred megabytes, but
>> slowly starts increasing again.  It gets old having to either logout or
>> restart the thing. 
>>
>> Has anyone else noticed this happening on their systems?  If not, I may
>> rename .kde4 and see if that helps.  Maybe a bad or outdated config. 
>>
>> Currently on:
>>
>> kde-plasma/plasma-workspace-5.10.5-r1
>>
>> Was on:
>>
>> kde-plasma/plasma-workspace-5.10.5
>>
>> It seems it was a Gentoo upgrade based on the -r1. 
>>
>> Thanks.
>>
>> Dale
>>
>> :-)  :-) 
>>
>
> Just a FYI for anyone else having this issue.  I just upgraded and it is
> still doing the same thing.  I'd think if it was a bug in the package
> that it would be fixed. 
>
> I think I'm going to try renaming .kde4 and see if a fresh start helps
> with this problem. 
>
> Dale
>
> :-)  :-) 
>


Well, giving it a fresh start may have made it worse.  It used to go a
day or so and now, I have to restart the thing every few hours.  When I
restart it uses about 2% of memory, maybe a little less.  After just a
few hours, it is already up to 7% and headed to 8%.  Thing is, it seems
to grow faster as it goes.  Currently on:

plasma-workspace-5.11.0

If anyone runs up on this in a search, I'm not aware of a solution, yet. 

Dale

:-)  :-) 


  parent reply	other threads:[~2017-10-17  8:23 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
2017-10-17  8:23   ` Dale [this message]
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=cc3d44e2-9533-6156-1f95-b6a395762686@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