Plasmashell consuming huge amounts of memory.

classic Classic list List threaded Threaded
15 messages Options
Reply | Threaded
Open this post in threaded view
|

Plasmashell consuming huge amounts of memory.

Dale-46
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

:-)  :-) 

Reply | Threaded
Open this post in threaded view
|

Re: Plasmashell consuming huge amounts of memory.

P Levine
On Wed, Oct 11, 2017 at 7:28 PM, Dale <[hidden email]> wrote:
Howdy,

I did a upgrade recently and after that, plasmashell is consuming a huge
amount of memory. 


Try seeing if this patch applies cleanly to dev-qt/qtdeclarative and if merging it resolves the issue: 

Reply | Threaded
Open this post in threaded view
|

Re: Plasmashell consuming huge amounts of memory.

Dale-46
P Levine wrote:
On Wed, Oct 11, 2017 at 7:28 PM, Dale <[hidden email]> wrote:
Howdy,

I did a upgrade recently and after that, plasmashell is consuming a huge
amount of memory. 


Try seeing if this patch applies cleanly to dev-qt/qtdeclarative and if merging it resolves the issue: 



I followed the directions here:

https://wiki.gentoo.org/wiki//etc/portage/patches

I've done it a couple times before, still have some patches there now, but wanted to be sure I didn't miss anything.  However, when I tell it to reemerge dev-qt/qtdeclarative, it doesn't apply the patch.  Usually it has a line that the patch was applied early on but I never seen it.  Odds are, I'm missing something somewhere.  I'll look into it more later. 

Thanks much.

Dale

:-)  :-) 
Reply | Threaded
Open this post in threaded view
|

Re: Plasmashell consuming huge amounts of memory.

P Levine
What version of dev-qt/qtdeclarative is being installed?


On Wed, Oct 11, 2017 at 11:09 PM, Dale <[hidden email]> wrote:
P Levine wrote:
On Wed, Oct 11, 2017 at 7:28 PM, Dale <[hidden email]> wrote:
Howdy,

I did a upgrade recently and after that, plasmashell is consuming a huge
amount of memory. 


Try seeing if this patch applies cleanly to dev-qt/qtdeclarative and if merging it resolves the issue: 



I followed the directions here:

https://wiki.gentoo.org/wiki//etc/portage/patches

I've done it a couple times before, still have some patches there now, but wanted to be sure I didn't miss anything.  However, when I tell it to reemerge dev-qt/qtdeclarative, it doesn't apply the patch.  Usually it has a line that the patch was applied early on but I never seen it.  Odds are, I'm missing something somewhere.  I'll look into it more later. 

Thanks much.

Dale

:-)  :-) 

Reply | Threaded
Open this post in threaded view
|

Re: Plasmashell consuming huge amounts of memory.

Dale-46
Hi,

It's trying to install dev-qt/qtdeclarative-5.9.2.  I went back and sort of started from the start.  Figured out where I made a boo boo.  Now it tries to apply the patch but fails to apply properly.  This is the error I get. 



>>> Emerging (1 of 1) dev-qt/qtdeclarative-5.9.2::gentoo
 * qtdeclarative-opensource-src-5.9.2.tar.xz SHA256 SHA512 WHIRLPOOL size ;-) ...                                                                                    [ ok ]
>>> Unpacking source...
>>> Unpacking qtdeclarative-opensource-src-5.9.2.tar.xz to /var/tmp/portage/dev-qt/qtdeclarative-5.9.2/work
>>> Source unpacked in /var/tmp/portage/dev-qt/qtdeclarative-5.9.2/work
>>> Preparing source in /var/tmp/portage/dev-qt/qtdeclarative-5.9.2/work/qtdeclarative-opensource-src-5.9.2 ...
 * Applying memory.patch ...
1 out of 1 hunk FAILED -- saving rejects to file src/quick/scenegraph/qsgthreadedrenderloop.cpp.rej
2 out of 2 hunks FAILED -- saving rejects to file src/quick/scenegraph/util/qsgatlastexture.cpp.rej
1 out of 1 hunk FAILED -- saving rejects to file src/quick/scenegraph/util/qsgatlastexture_p.h.rej                                                                   [ !! ]
 * ERROR: dev-qt/qtdeclarative-5.9.2::gentoo failed (prepare phase):
 *   patch -p1  failed with /etc/portage/patches/dev-qt/qtdeclarative-5.9.2/memory.patch
 *
 * Call stack:
 *               ebuild.sh, line  115:  Called src_prepare
 *             environment, line 3798:  Called qt5-build_src_prepare
 *             environment, line 3432:  Called default
 *      phase-functions.sh, line  808:  Called default_src_prepare
 *      phase-functions.sh, line  873:  Called __eapi6_src_prepare
 *             environment, line  273:  Called eapply_user
 *             environment, line  979:  Called eapply '/etc/portage/patches/dev-qt/qtdeclarative-5.9.2/memory.patch'
 *             environment, line  949:  Called _eapply_patch '/etc/portage/patches/dev-qt/qtdeclarative-5.9.2/memory.patch'
 *             environment, line  887:  Called __helpers_die 'patch -p1  failed with /etc/portage/patches/dev-qt/qtdeclarative-5.9.2/memory.patch'
 *   isolated-functions.sh, line  117:  Called die
 * The specific snippet of code:
 *              die "$@"
 *
 * If you need support, post the output of `emerge --info '=dev-qt/qtdeclarative-5.9.2::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=dev-qt/qtdeclarative-5.9.2::gentoo'`.
 * The complete build log is located at '/var/log/portage/dev-qt:qtdeclarative-5.9.2:20171012-043431.log'.
 * For convenience, a symlink to the build log is located at '/var/tmp/portage/dev-qt/qtdeclarative-5.9.2/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-qt/qtdeclarative-5.9.2/temp/environment'.
 * Working directory: '/var/tmp/portage/dev-qt/qtdeclarative-5.9.2/work/qtdeclarative-opensource-src-5.9.2'
 * S: '/var/tmp/portage/dev-qt/qtdeclarative-5.9.2/work/qtdeclarative-opensource-src-5.9.2'

>>> Failed to emerge dev-qt/qtdeclarative-5.9.2, Log file:

>>>  '/var/log/portage/dev-qt:qtdeclarative-5.9.2:20171012-043431.log'
 *
 * The following package has failed to build, install, or execute postinst:
 *
 *  (dev-qt/qtdeclarative-5.9.2:5/5.9::gentoo, ebuild scheduled for merge), Log file:
 *   '/var/log/portage/dev-qt:qtdeclarative-5.9.2:20171012-043431.log'
 *
root@fireball / #


Maybe this is due to it being for a different version or something.  I dunno. 

If needed, I may go back to a older version for a bit but suspect it to be a bit of a hassle. 

Dale

:-)  :-) 



P Levine wrote:
What version of dev-qt/qtdeclarative is being installed?


On Wed, Oct 11, 2017 at 11:09 PM, Dale <[hidden email]> wrote:
P Levine wrote:
On Wed, Oct 11, 2017 at 7:28 PM, Dale <[hidden email]> wrote:
Howdy,

I did a upgrade recently and after that, plasmashell is consuming a huge
amount of memory. 


Try seeing if this patch applies cleanly to dev-qt/qtdeclarative and if merging it resolves the issue: 



I followed the directions here:

https://wiki.gentoo.org/wiki//etc/portage/patches

I've done it a couple times before, still have some patches there now, but wanted to be sure I didn't miss anything.  However, when I tell it to reemerge dev-qt/qtdeclarative, it doesn't apply the patch.  Usually it has a line that the patch was applied early on but I never seen it.  Odds are, I'm missing something somewhere.  I'll look into it more later. 

Thanks much.

Dale

:-)  :-) 


Reply | Threaded
Open this post in threaded view
|

Re: Plasmashell consuming huge amounts of memory.

P Levine
On Thu, Oct 12, 2017 at 12:40 AM, Dale <[hidden email]> wrote:
Hi,

It's trying to install dev-qt/qtdeclarative-5.9.2.  I went back and sort of started from the start.  Figured out where I made a boo boo.  Now it tries to apply the patch but fails to apply properly. 
 
​If you don't already​
 
​have ​dev-qt/qtdeclarative-5.9.2 installed then install it without the patch.  Otherwise, I can't help you.  The patch was just meant to be an attempt at a backport for a lesser version of​ dev-qt/qtdeclarative.

Reply | Threaded
Open this post in threaded view
|

Re: Plasmashell consuming huge amounts of memory.

Dale-46
P Levine wrote:
On Thu, Oct 12, 2017 at 12:40 AM, Dale <[hidden email]> wrote:
Hi,

It's trying to install dev-qt/qtdeclarative-5.9.2.  I went back and sort of started from the start.  Figured out where I made a boo boo.  Now it tries to apply the patch but fails to apply properly. 
 
​If you don't already​
 
​have ​dev-qt/qtdeclarative-5.9.2 installed then install it without the patch.  Otherwise, I can't help you.  The patch was just meant to be an attempt at a backport for a lesser version of​ dev-qt/qtdeclarative.



Well, that is the version that started the memory hogging.  Since my last restart, it seems to not be hogging up memory, yet anyway. 

I tried to go back a version but it is causing all sorts of havoc.  I was having to remove unmask/keyword entries and add mask entries and it was just going round and round.  May just wait a bit and see if a new update comes out with a fix. 

Thanks for trying tho.  At least it is possible that this is affecting enough users that it will get fixed. 

Dale

:-)  :-) 
Reply | Threaded
Open this post in threaded view
|

Re: Plasmashell consuming huge amounts of memory.

Dale-46
In reply to this post by Dale-46
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

:-)  :-) 

Reply | Threaded
Open this post in threaded view
|

Re: Plasmashell consuming huge amounts of memory.

P Levine
On Mon, Oct 16, 2017 at 8:41 PM, Dale <[hidden email]> wrote:
I think I'm going to try renaming .kde4 and see if a fresh start helps
with this problem. 

​AFAIK, plasma5 uses ~/.local and ~/​.config.

Reply | Threaded
Open this post in threaded view
|

Re: Plasmashell consuming huge amounts of memory.

Philip Webb-2
In reply to this post by Dale-46
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

--
========================,,============================================
SUPPORT     ___________//___,   Philip Webb
ELECTRIC   /] [] [] [] [] []|   Cities Centre, University of Toronto
TRANSIT    `-O----------O---'   purslowatchassdotutorontodotca


Reply | Threaded
Open this post in threaded view
|

Re: Plasmashell consuming huge amounts of memory.

Dale-46
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

:-)  :-) 

Reply | Threaded
Open this post in threaded view
|

Re: Plasmashell consuming huge amounts of memory.

Dale-46
In reply to this post by P Levine
P Levine wrote:
On Mon, Oct 16, 2017 at 8:41 PM, Dale <[hidden email]> wrote:
I think I'm going to try renaming .kde4 and see if a fresh start helps
with this problem. 

​AFAIK, plasma5 uses ~/.local and ~/​.config.



I wish I had read this earlier.  I keep forgetting that.  I've read it before but I never seem to recall it when I really really need it.  If I ever remember to do just those two files, I'll remember it most likely.  Big IF there.

Thanks.

Dale

:-)  :-) 
Reply | Threaded
Open this post in threaded view
|

Re: Plasmashell consuming huge amounts of memory.

Dale-46
In reply to this post by Dale-46
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

:-)  :-) 

Reply | Threaded
Open this post in threaded view
|

Re: Plasmashell consuming huge amounts of memory.

Peter Humphrey-3
In reply to this post by Dale-46
On Tuesday, 17 October 2017 04:03:14 BST Dale wrote:
> P Levine wrote:
> > ​AFAIK, plasma5 uses ~/.local and ~/​.config.
>
> I wish I had read this earlier.  I keep forgetting that.  I've read it
> before but I never seem to recall it when I really really need it.  If I
> ever remember to do just those two files, I'll remember it most likely.
> Big IF there.

Having struggled monumentally with KMail over the last several months, I got
fed up enough with setting up a new user from scratch that I now have a
fresh user set up and ready to go. It has the few things I want to keep in
my own account, and an empty directory structure for KMail. All I have to do
is (re)move the old account, copy the ready account into place and go.

That would be harder if I didn't have a ~/common partition containing
everything I'd need if I installed another distro but without the version-
specific KDE stuff. It's a hangover from the days when I hadn't settled on a
single distro, but it's proved its worth this year.

--
Regards,
Peter.


Reply | Threaded
Open this post in threaded view
|

Re: Plasmashell consuming huge amounts of memory.

Dale-46
Peter Humphrey wrote:

> On Tuesday, 17 October 2017 04:03:14 BST Dale wrote:
>> P Levine wrote:
>>> ​AFAIK, plasma5 uses ~/.local and ~/​.config.
>> I wish I had read this earlier.  I keep forgetting that.  I've read it
>> before but I never seem to recall it when I really really need it.  If I
>> ever remember to do just those two files, I'll remember it most likely.
>> Big IF there.
> Having struggled monumentally with KMail over the last several months, I got
> fed up enough with setting up a new user from scratch that I now have a
> fresh user set up and ready to go. It has the few things I want to keep in
> my own account, and an empty directory structure for KMail. All I have to do
> is (re)move the old account, copy the ready account into place and go.
>
> That would be harder if I didn't have a ~/common partition containing
> everything I'd need if I installed another distro but without the version-
> specific KDE stuff. It's a hangover from the days when I hadn't settled on a
> single distro, but it's proved its worth this year.
>


I switched from Kmail ages ago.  I think it was because clicking links
was becoming a nightmare.  It's been so long, can't be sure.  I switched
to Seamonkey which means I shouldn't have to move emails unless I switch
email programs.  Of course, Seamonkey gets on my nerves at times too and
I figure at some point, I'm going to blast it with a cannon or something
right out the door. 

For some reason, the mv command did something weird.  For a bit there, I
thought I'd lost my emails.  However, I found them and copied them back
into the right place. 

I just wish I had either remembered or seen Levine's comment before I
did all that.  That could have saved me a lot of trouble.  Most likely
just renaming those two files would be a good test. 

BTW, I've already had to restart the plasma thing.  It was up to almost
20%.  Since I don't shutdown my puter, I kill it before I lay down for a
nap.  Restart it when I get up.  Hoping for a can of Raid soon.  :/

Dale

:-)  :-)