[gentoo-user] sddm-helper and high memory usage

[gentoo-user] sddm-helper and high memory usage

[Dale]

Howdy,

I been noticing that sddm is using a lot of memory.  In the past, it
would use a few hundred megabytes but nothing out of the norm for a GUI
command.  This is what ps aux shows.



USER       PID   %CPU %MEM    VSZ       RSS      TTY  STAT START   TIME
COMMAND
root       19256  1.0    10.3   3443932 3400112 ?     S    02:40   6:36
/usr/libexec/sddm-helper --socket
/tmp/sddm-auth8e2859d9-6da1-4071-b479-b9caa969c3d8 --id 1 --start
/usr/bin/startplasma-x11 --user dale



When it did this the other day, I closed all my programs so I could
logout, reset and log back in again.  After I hit logout, I noticed the
little memory usage meter on the bottom of my screen was down to a more
normal level.  It was already logging me out so to late to stop it.  It
seems that it dropped after I closed Firefox.  I tend to have two
profiles running and they use quite a bit of memory on their own.  The
new thing is sddm using this much as well.  Could Firefox have some
effect on this??

When I first login, it is using the normal amount of memory. It seems to
build up from there.  Once it hits around 13 or 14%, it seems to stop
using any more.  I've let it run for a while and it seems to stop there. 

I'm pretty sure I upgraded sddm the other day.  This is where I'm at
right now.

kde-plasma/sddm-kcm-5.18.4.1
x11-misc/sddm-0.18.1-r1

Is anyone else noticing this?  I would go back a version but it is
masked, I'm assuming it has some known issues that may be worse than this. 

I might add, while I normally switch to the boot runlevel and back again
after a upgrade, I did have to shutdown last night.  I was trying to
replace my UPS batteries.  My new batteries are about 1/4" to tall.  New
set on the way.  Anyway, it is doing this even after a fresh power up.

I did a bug search on BGO but didn't see anything like this.

Any ideas? 

Dale

:-)  :-) 

Re: [gentoo-user] sddm-helper and high memory usage

[Dale]

[-- Attachment #1: Type: text/plain, Size: 1083 bytes --]

Dale wrote:
> Howdy,
>
> <<<SNIP>>>
> When it did this the other day, I closed all my programs so I could
> logout, reset and log back in again.  After I hit logout, I noticed the
> little memory usage meter on the bottom of my screen was down to a more
> normal level.  It was already logging me out so to late to stop it.  It
> seems that it dropped after I closed Firefox.  I tend to have two
> profiles running and they use quite a bit of memory on their own.  The
> new thing is sddm using this much as well.  Could Firefox have some
> effect on this??
>
> <<<SNIP>>>
> Any ideas? 
>
> Dale
>
> :-)  :-) 
>


Ignore the part about Firefox.  I noticed it was up to about 4.3GBs or
13.5% again and closed all my browsers.  After that was done and it
settled a bit, it was using the same amount of memory.  Closing my
browsers has no effect on it's memory usage.  Logging out and back in
again, back to normal.  I'm sure it will start rising again tho.

Still curious to see if anyone else has this issue or has a idea on how
to fix it. 

Thanks.

Dale

:-)  :-) 

[-- Attachment #2: Type: text/html, Size: 1544 bytes --]

Re: [gentoo-user] sddm-helper and high memory usage

[Michael]

[-- Attachment #1: Type: text/plain, Size: 2749 bytes --]

On Thursday, 30 April 2020 21:14:05 BST Dale wrote:
> Dale wrote:
> > Howdy,
> > 
> > <<<SNIP>>>
> > When it did this the other day, I closed all my programs so I could
> > logout, reset and log back in again.  After I hit logout, I noticed the
> > little memory usage meter on the bottom of my screen was down to a more
> > normal level.  It was already logging me out so to late to stop it.  It
> > seems that it dropped after I closed Firefox.  I tend to have two
> > profiles running and they use quite a bit of memory on their own.  The
> > new thing is sddm using this much as well.  Could Firefox have some
> > effect on this??
> > 
> > <<<SNIP>>>
> > Any ideas? 
> > 
> > Dale
> > 
> > :-)  :-) 
> 
> Ignore the part about Firefox.  I noticed it was up to about 4.3GBs or
> 13.5% again and closed all my browsers.  After that was done and it
> settled a bit, it was using the same amount of memory.  Closing my
> browsers has no effect on it's memory usage.  Logging out and back in
> again, back to normal.  I'm sure it will start rising again tho.
> 
> Still curious to see if anyone else has this issue or has a idea on how
> to fix it. 
> 
> Thanks.
> 
> Dale
> 
> :-)  :-) 

I'm running stable here and have not noticed sddm eating up much memory on a 
single user PC with 16G RAM.  I'm not running FF at this moment, but Kmail, 
plus a tonne of akonadi sql processes, plus gkrellms.  However, sddm shouldn't 
be consuming much RAM beyond passing authentication credentials to X and 
starting a session, dynamically pulling in dbus & syslog.

My sddm config has not been changed from defaults, but I have switched the 
theme to Elarun via Plasma's SystemSettings.  I use no icon for avatar.  The X 
session memory usage changes, but sddm is pretty much stable from what I 
observed.

USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root      3822  0.0  0.0 136480 15324 ?        Ssl  15:37   0:00 /usr/bin/sddm
root      3888  4.1  0.5 1384204 85148 tty7    Ssl+ 15:37   1:42 /usr/bin/X -
nolisten tcp -auth /var/run/sddm/{long_string_here} -background none -noreset 
-displayfd 17 -seat seat0 vt7
sddm      3961  0.0  0.0   4552  2264 ?        S    15:37   0:00 dbus-launch 
--autolaunch long_string_here --binary-syntax --close-stderr
sddm      3962  0.0  0.0   3868  1948 ?        Ss   15:37   0:00 /usr/bin/
dbus-daemon --syslog-only --fork --print-pid 5 --print-address 7 --session
root      4030  0.0  0.0  54516 14020 ?        S    15:38   0:00 /usr/libexec/
sddm-helper --socket /tmp/sddm-auth0472070a-360a-4d6f-9715-b06b8f18b464 --id 1 
--start /usr/bin/startplasma-x11 --user michael
michael  10000  0.0  0.0   7964   752 pts/1    S+   16:18   0:00 /bin/grep -E 
--colour=auto --color=auto USER|sddm


[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] sddm-helper and high memory usage

[Dale]

[-- Attachment #1: Type: text/plain, Size: 3927 bytes --]

Michael wrote:
> On Thursday, 30 April 2020 21:14:05 BST Dale wrote:
>> Dale wrote:
>>> Howdy,
>>>
>>> <<<SNIP>>>
>>> When it did this the other day, I closed all my programs so I could
>>> logout, reset and log back in again.  After I hit logout, I noticed the
>>> little memory usage meter on the bottom of my screen was down to a more
>>> normal level.  It was already logging me out so to late to stop it.  It
>>> seems that it dropped after I closed Firefox.  I tend to have two
>>> profiles running and they use quite a bit of memory on their own.  The
>>> new thing is sddm using this much as well.  Could Firefox have some
>>> effect on this??
>>>
>>> <<<SNIP>>>
>>> Any ideas? 
>>>
>>> Dale
>>>
>>> :-)  :-) 
>> Ignore the part about Firefox.  I noticed it was up to about 4.3GBs or
>> 13.5% again and closed all my browsers.  After that was done and it
>> settled a bit, it was using the same amount of memory.  Closing my
>> browsers has no effect on it's memory usage.  Logging out and back in
>> again, back to normal.  I'm sure it will start rising again tho.
>>
>> Still curious to see if anyone else has this issue or has a idea on how
>> to fix it. 
>>
>> Thanks.
>>
>> Dale
>>
>> :-)  :-) 
> I'm running stable here and have not noticed sddm eating up much memory on a 
> single user PC with 16G RAM.  I'm not running FF at this moment, but Kmail, 
> plus a tonne of akonadi sql processes, plus gkrellms.  However, sddm shouldn't 
> be consuming much RAM beyond passing authentication credentials to X and 
> starting a session, dynamically pulling in dbus & syslog.
>
> My sddm config has not been changed from defaults, but I have switched the 
> theme to Elarun via Plasma's SystemSettings.  I use no icon for avatar.  The X 
> session memory usage changes, but sddm is pretty much stable from what I 
> observed.
>
> USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
> root      3822  0.0  0.0 136480 15324 ?        Ssl  15:37   0:00 /usr/bin/sddm
> root      3888  4.1  0.5 1384204 85148 tty7    Ssl+ 15:37   1:42 /usr/bin/X -
> nolisten tcp -auth /var/run/sddm/{long_string_here} -background none -noreset 
> -displayfd 17 -seat seat0 vt7
> sddm      3961  0.0  0.0   4552  2264 ?        S    15:37   0:00 dbus-launch 
> --autolaunch long_string_here --binary-syntax --close-stderr
> sddm      3962  0.0  0.0   3868  1948 ?        Ss   15:37   0:00 /usr/bin/
> dbus-daemon --syslog-only --fork --print-pid 5 --print-address 7 --session
> root      4030  0.0  0.0  54516 14020 ?        S    15:38   0:00 /usr/libexec/
> sddm-helper --socket /tmp/sddm-auth0472070a-360a-4d6f-9715-b06b8f18b464 --id 1 
> --start /usr/bin/startplasma-x11 --user michael
> michael  10000  0.0  0.0   7964   752 pts/1    S+   16:18   0:00 /bin/grep -E 
> --colour=auto --color=auto USER|sddm
>


What you post is about what it used to do.  Last night I rebuilt
everything equery d sddm returned plus a couple extra packages as well. 
I logged out, logged back in and while better, it is still using to much
memory.  This is the current usage and it has been steady for a few
hours now.


USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root     20325  0.2  1.2 458860 418280 ?       S    05:20   0:53
/usr/libexec/sddm-helper --socket
/tmp/sddm-auth09e6b5a4-8a3d-42d5-9068-eefeecc22458 --id 1 --start
/usr/bin/startplasma-x11 --user dale


While it is better, it should be a lot less than that.  I have 32GBs
here so even 1.2% is a good bit.  I'm starting to run revdep-rebuild as
I type.  I'll see if it catches anything.  If not and it keeps doing
this, I may do a emerge -e world which should catch any sort of
linking/depends problems. 

I wonder if this has anything to do with my wallpapers??  That caused
other issues a while back but surely not. 

Thanks for the info.  At least it seems to just be me. 

Dale

:-)  :-) 

[-- Attachment #2: Type: text/html, Size: 4561 bytes --]

Re: [gentoo-user] sddm-helper and high memory usage

[Dale]

Dale wrote:
>
> I wonder if this has anything to do with my wallpapers??  That caused
> other issues a while back but surely not. 
>
> Thanks for the info.  At least it seems to just be me. 
>
> Dale
>
> :-)  :-) 


Little update.  This problem must have been caused by something plasma
related.  KDE sent a announcement that a new plasma update was
available.  It took a day or two to hit the tree but I noticed last
night it was available.  I usually do my updates on Sunday evening but
did them last night because of this problem.  I did the build in my
chroot overnight and installed on the live system early this morning. 
So far, it is using memory like it used to.  This is what ps shows for
it, easiest command I know to show it. 


root@fireball / # ps aux | grep sddm-helper
root      1384  0.0  0.0   7652   748 pts/8    S+   12:31   0:00 grep
--colour=auto -i sddm-helper
root     30358  0.7  0.8 325016 283652 ?       S    09:15   1:23
/usr/libexec/sddm-helper --socket
/tmp/sddm-auth06120d08-7716-49c0-9a70-8232396b69bf --id 1 --start
/usr/bin/startplasma-x11 --user dale
root@fireball / # ps aux | grep sddm-helper
root      9218  0.0  0.0   7652   748 pts/8    S+   13:47   0:00 grep
--colour=auto -i sddm-helper
root     30358  0.5  0.8 325284 283916 ?       S    09:15   1:23
/usr/libexec/sddm-helper --socket
/tmp/sddm-auth06120d08-7716-49c0-9a70-8232396b69bf --id 1 --start
/usr/bin/startplasma-x11 --user dale
root@fireball / #


The first one was ran shortly after I got logged in and the second was
ran just a few minutes ago, several hours later.  Usually by this time
it would be up around 2% or more.  It's seems to be rising but it is
much slower.  It could just be normal that it fluctuates a bit too. 

I guess the bug was caught and fixed.  Thanks to all that read and
Michael for trying to help. 

Dale

:-)  :-) 

Re: [gentoo-user] sddm-helper and high memory usage

[Dale]

[-- Attachment #1: Type: text/plain, Size: 2428 bytes --]

Dale wrote:
>
> I guess the bug was caught and fixed.  Thanks to all that read and
> Michael for trying to help. 
>
> Dale
>
> :-)  :-) 
>

I have some more info and some doesn't make much sense.  I thought this
might be fixed but guess not.  While it is somewhat slower to take up a
lot of memory after a recent plasma update, it does still get there.  It
takes a day or so now where before it was just a few hours.  Logging out
and back in does reset it to normal tho. 

One thing that seems to stand out, Firefox and one profile in
particular.  I have two profiles that I use a lot nowadays.  One is for
ebay, Amazon, tracking shipments etc etc.  The other is where I do
youtube and other video type sites.  It has a video download helper
add-on installed but the rest is mostly the same.  When I have the first
profile open, it is slow to consume memory.  When I open the one I use
for videos, it starts building up faster.  While I can logout and back
in daily, it still gets to around 5% or so.  I usually start planning to
logout and back in when it hits 4% or so.  It's at 5 by the time I get
everything to where I can.  Thing is, closing Firefox doesn't seem to
have any effect on it.  It slows down some but doesn't get back to
normal memory usage.  I can't quite figure out how Firefox can have a
effect on it tho.  I realize it is running within the GUI and all but
still, it doesn't make much sense. 

I do a emerge -e system and world the other day in my chroot.  Once
done, I did a complete re-emerge on my running system.  All was done
with the same gcc, 9.3.  I'm not sure it did any good but at least it
rules out some sort of mismatch with different packages running with
different gcc versions.  It also rules out and sort of broken linkages
and other mismatches as well.  I've also updated kernels and video
drivers with no change.  I also disabled my background slideshow to see
if it was causing this, no change.  When I was doing my emerge system
and world, I had Firefox and at times Seamonkey closed and it stayed
within reason at least.  It would get up to around 2% but seemed to stay
there.  I'm not sure what to look for or even for sure what is exactly
the trigger for this problem.  It seems Firefox affects it but not sure
why that is exactly. 

If anyone has ideas, I'm open to them.  I can't think of anything else
to try at the moment. 

Dale

:-)  :-) 

[-- Attachment #2: Type: text/html, Size: 2987 bytes --]

Re: [gentoo-user] sddm-helper and high memory usage

[Michael]

[-- Attachment #1: Type: text/plain, Size: 3069 bytes --]

On Saturday, 16 May 2020 13:32:32 BST Dale wrote:
> Dale wrote:
> > I guess the bug was caught and fixed.  Thanks to all that read and
> > Michael for trying to help. 
> > 
> > Dale
> > 
> > :-)  :-) 
> 
> I have some more info and some doesn't make much sense.  I thought this
> might be fixed but guess not.  While it is somewhat slower to take up a
> lot of memory after a recent plasma update, it does still get there.  It
> takes a day or so now where before it was just a few hours.  Logging out
> and back in does reset it to normal tho. 
> 
> One thing that seems to stand out, Firefox and one profile in
> particular.  I have two profiles that I use a lot nowadays.  One is for
> ebay, Amazon, tracking shipments etc etc.  The other is where I do
> youtube and other video type sites.  It has a video download helper
> add-on installed but the rest is mostly the same.  When I have the first
> profile open, it is slow to consume memory.  When I open the one I use
> for videos, it starts building up faster.  While I can logout and back
> in daily, it still gets to around 5% or so.  I usually start planning to
> logout and back in when it hits 4% or so.  It's at 5 by the time I get
> everything to where I can.  Thing is, closing Firefox doesn't seem to
> have any effect on it.  It slows down some but doesn't get back to
> normal memory usage.  I can't quite figure out how Firefox can have a
> effect on it tho.  I realize it is running within the GUI and all but
> still, it doesn't make much sense. 
> 
> I do a emerge -e system and world the other day in my chroot.  Once
> done, I did a complete re-emerge on my running system.  All was done
> with the same gcc, 9.3.  I'm not sure it did any good but at least it
> rules out some sort of mismatch with different packages running with
> different gcc versions.  It also rules out and sort of broken linkages
> and other mismatches as well.  I've also updated kernels and video
> drivers with no change.  I also disabled my background slideshow to see
> if it was causing this, no change.  When I was doing my emerge system
> and world, I had Firefox and at times Seamonkey closed and it stayed
> within reason at least.  It would get up to around 2% but seemed to stay
> there.  I'm not sure what to look for or even for sure what is exactly
> the trigger for this problem.  It seems Firefox affects it but not sure
> why that is exactly. 
> 
> If anyone has ideas, I'm open to them.  I can't think of anything else
> to try at the moment. 
> 
> Dale
> 
> :-)  :-) 


Just an idea:

Log out/in, check memory usage is normal.  If not log out, restart /etc/
init.d/xdm and login again.  Start FF without any addons.  Use a new profile 
if necessary.  Check memory usage.  If after a while under normal use you 
still have reasonable levels of memory usage, then you can start adding one 
add-on at a time and see where that gets you.

You may also want to give youtube-dl a spin.  I know, it's not a FF-GUI video 
download tool, but it works without getting in the way or eating up RAM 
unnecessarily.

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] sddm-helper and high memory usage

[Dale]

[-- Attachment #1: Type: text/plain, Size: 4698 bytes --]

Michael wrote:
> On Saturday, 16 May 2020 13:32:32 BST Dale wrote:
>> Dale wrote:
>>> I guess the bug was caught and fixed.  Thanks to all that read and
>>> Michael for trying to help. 
>>>
>>> Dale
>>>
>>> :-)  :-) 
>> I have some more info and some doesn't make much sense.  I thought this
>> might be fixed but guess not.  While it is somewhat slower to take up a
>> lot of memory after a recent plasma update, it does still get there.  It
>> takes a day or so now where before it was just a few hours.  Logging out
>> and back in does reset it to normal tho. 
>>
>> One thing that seems to stand out, Firefox and one profile in
>> particular.  I have two profiles that I use a lot nowadays.  One is for
>> ebay, Amazon, tracking shipments etc etc.  The other is where I do
>> youtube and other video type sites.  It has a video download helper
>> add-on installed but the rest is mostly the same.  When I have the first
>> profile open, it is slow to consume memory.  When I open the one I use
>> for videos, it starts building up faster.  While I can logout and back
>> in daily, it still gets to around 5% or so.  I usually start planning to
>> logout and back in when it hits 4% or so.  It's at 5 by the time I get
>> everything to where I can.  Thing is, closing Firefox doesn't seem to
>> have any effect on it.  It slows down some but doesn't get back to
>> normal memory usage.  I can't quite figure out how Firefox can have a
>> effect on it tho.  I realize it is running within the GUI and all but
>> still, it doesn't make much sense. 
>>
>> I do a emerge -e system and world the other day in my chroot.  Once
>> done, I did a complete re-emerge on my running system.  All was done
>> with the same gcc, 9.3.  I'm not sure it did any good but at least it
>> rules out some sort of mismatch with different packages running with
>> different gcc versions.  It also rules out and sort of broken linkages
>> and other mismatches as well.  I've also updated kernels and video
>> drivers with no change.  I also disabled my background slideshow to see
>> if it was causing this, no change.  When I was doing my emerge system
>> and world, I had Firefox and at times Seamonkey closed and it stayed
>> within reason at least.  It would get up to around 2% but seemed to stay
>> there.  I'm not sure what to look for or even for sure what is exactly
>> the trigger for this problem.  It seems Firefox affects it but not sure
>> why that is exactly. 
>>
>> If anyone has ideas, I'm open to them.  I can't think of anything else
>> to try at the moment. 
>>
>> Dale
>>
>> :-)  :-) 
>
> Just an idea:
>
> Log out/in, check memory usage is normal.  If not log out, restart /etc/
> init.d/xdm and login again.  Start FF without any addons.  Use a new profile 
> if necessary.  Check memory usage.  If after a while under normal use you 
> still have reasonable levels of memory usage, then you can start adding one 
> add-on at a time and see where that gets you.
>
> You may also want to give youtube-dl a spin.  I know, it's not a FF-GUI video 
> download tool, but it works without getting in the way or eating up RAM 
> unnecessarily.

I have a test Firefox profile that has very few if any add-ons
installed.  I sometimes use it to test problems.  Anyway, I suspect the
video download add-on myself.  Ever since the big change with add-ons
and multi-process support, the video add-on has had issues.  I've had
crashes, excessive memory usage by Firefox itself etc etc.  For the most
part, the video add-on works but it is not like it was with the older
versions of Firefox.  While sddm-helper does use more memory even
without Firefox, it just gets much worse with it. 

I have and use youtube-dl.  I use it for youtube and a couple other
sites that it works with.  Thing is, some sites don't work with
youtube-dl.  It tries but it reports some sort of error, error varies
from site to site, and then stops.  I wish it would work because it is
drop dead easy to use once you get it configured.  I've got mine set up
pretty well.  It will try to get 1280x720 but no larger if available. 
For what I do 99% of the time, that works very well.  File size is
manageable but has a good resolution.  Of course some older videos are
480 or something but still, I like the tool. 

I see another KDE upgrade being released.  It is a plasma update so
hopefully it will hit the tree by Sunday.  Maybe it will have a fix or
something.  In the meantime, I'll keep observing and trying things to
see if I can figure out what is going on.  It's confusing tho. 

Thanks.  Will try to the test profile shortly.  I'm at 6% or so right
now.  Time for a reset anyway. 

Dale

:-)  :-) 

[-- Attachment #2: Type: text/html, Size: 5254 bytes --]

Re: [gentoo-user] sddm-helper and high memory usage

[J. Roeleveld]

On Sunday, May 17, 2020 12:09:19 AM CEST Dale wrote:
> Michael wrote:
> > On Saturday, 16 May 2020 13:32:32 BST Dale wrote:
> >> Dale wrote:
> >>> I guess the bug was caught and fixed.  Thanks to all that read and
> >>> Michael for trying to help.
> >>> 
> >>> Dale
> >>> 
> >>> :-)  :-)
> >> 
> >> I have some more info and some doesn't make much sense.  I thought this
> >> might be fixed but guess not.  While it is somewhat slower to take up a
> >> lot of memory after a recent plasma update, it does still get there.  It
> >> takes a day or so now where before it was just a few hours.  Logging out
> >> and back in does reset it to normal tho.
> >> 
> >> One thing that seems to stand out, Firefox and one profile in
> >> particular.  I have two profiles that I use a lot nowadays.  One is for
> >> ebay, Amazon, tracking shipments etc etc.  The other is where I do
> >> youtube and other video type sites.  It has a video download helper
> >> add-on installed but the rest is mostly the same.  When I have the first
> >> profile open, it is slow to consume memory.  When I open the one I use
> >> for videos, it starts building up faster.  While I can logout and back
> >> in daily, it still gets to around 5% or so.  I usually start planning to
> >> logout and back in when it hits 4% or so.  It's at 5 by the time I get
> >> everything to where I can.  Thing is, closing Firefox doesn't seem to
> >> have any effect on it.  It slows down some but doesn't get back to
> >> normal memory usage.  I can't quite figure out how Firefox can have a
> >> effect on it tho.  I realize it is running within the GUI and all but
> >> still, it doesn't make much sense.
> >> 
> >> I do a emerge -e system and world the other day in my chroot.  Once
> >> done, I did a complete re-emerge on my running system.  All was done
> >> with the same gcc, 9.3.  I'm not sure it did any good but at least it
> >> rules out some sort of mismatch with different packages running with
> >> different gcc versions.  It also rules out and sort of broken linkages
> >> and other mismatches as well.  I've also updated kernels and video
> >> drivers with no change.  I also disabled my background slideshow to see
> >> if it was causing this, no change.  When I was doing my emerge system
> >> and world, I had Firefox and at times Seamonkey closed and it stayed
> >> within reason at least.  It would get up to around 2% but seemed to stay
> >> there.  I'm not sure what to look for or even for sure what is exactly
> >> the trigger for this problem.  It seems Firefox affects it but not sure
> >> why that is exactly.
> >> 
> >> If anyone has ideas, I'm open to them.  I can't think of anything else
> >> to try at the moment.
> >> 
> >> Dale
> >> 
> >> :-)  :-)
> > 
> > Just an idea:
> > 
> > Log out/in, check memory usage is normal.  If not log out, restart /etc/
> > init.d/xdm and login again.  Start FF without any addons.  Use a new
> > profile if necessary.  Check memory usage.  If after a while under normal
> > use you still have reasonable levels of memory usage, then you can start
> > adding one add-on at a time and see where that gets you.
> > 
> > You may also want to give youtube-dl a spin.  I know, it's not a FF-GUI
> > video download tool, but it works without getting in the way or eating up
> > RAM unnecessarily.
> 
> I have a test Firefox profile that has very few if any add-ons
> installed.  I sometimes use it to test problems.  Anyway, I suspect the
> video download add-on myself.  Ever since the big change with add-ons
> and multi-process support, the video add-on has had issues.  I've had
> crashes, excessive memory usage by Firefox itself etc etc.  For the most
> part, the video add-on works but it is not like it was with the older
> versions of Firefox.  While sddm-helper does use more memory even
> without Firefox, it just gets much worse with it. 
> 
> I have and use youtube-dl.  I use it for youtube and a couple other
> sites that it works with.  Thing is, some sites don't work with
> youtube-dl.  It tries but it reports some sort of error, error varies
> from site to site, and then stops.  I wish it would work because it is
> drop dead easy to use once you get it configured.  I've got mine set up
> pretty well.  It will try to get 1280x720 but no larger if available. 
> For what I do 99% of the time, that works very well.  File size is
> manageable but has a good resolution.  Of course some older videos are
> 480 or something but still, I like the tool. 
> 
> I see another KDE upgrade being released.  It is a plasma update so
> hopefully it will hit the tree by Sunday.  Maybe it will have a fix or
> something.  In the meantime, I'll keep observing and trying things to
> see if I can figure out what is going on.  It's confusing tho. 
> 
> Thanks.  Will try to the test profile shortly.  I'm at 6% or so right
> now.  Time for a reset anyway. 

Dale,

The few times I have issues with "sddm-helper" is when I resume my laptop from 
hibernate. (Not always, but occasionally)
The issue I see is 100% CPU-usage and a black X-display. I can switch to 
console (CTRL+ALT+F1), login as root and kill the offending sddm-helper.
It gets restarted automatically and I see no issue.

Do you tend to lock your screen a lot? As it might be related to screensavers. 
(I have a simple static lock-screen, nothing remotely fancy)

Also, you can try killing "kill -9 sddm-helper" when it goes up and see what 
happens next.

Is there anything in the sddm-logs?
Mine, for some reason, writes to /var/log/sddm.log

Do you have anything special in your Xsession files and/or profiles (incl. 
bash_profile and bashrc) that is non-default?

Which login-theme do you use?

--
Joost

Re: [gentoo-user] sddm-helper and high memory usage

[Dale]

[-- Attachment #1: Type: text/plain, Size: 5349 bytes --]

J. Roeleveld wrote:
>
> Dale,
>
> The few times I have issues with "sddm-helper" is when I resume my laptop from 
> hibernate. (Not always, but occasionally)
> The issue I see is 100% CPU-usage and a black X-display. I can switch to 
> console (CTRL+ALT+F1), login as root and kill the offending sddm-helper.
> It gets restarted automatically and I see no issue.
>
> Do you tend to lock your screen a lot? As it might be related to screensavers. 
> (I have a simple static lock-screen, nothing remotely fancy)
>
> Also, you can try killing "kill -9 sddm-helper" when it goes up and see what 
> happens next.
>
> Is there anything in the sddm-logs?
> Mine, for some reason, writes to /var/log/sddm.log
>
> Do you have anything special in your Xsession files and/or profiles (incl. 
> bash_profile and bashrc) that is non-default?
>
> Which login-theme do you use?
>
> --
> Joost

Well, I didn't know I could kill that thing.  I been logging out and
back in which annoys the stuffing out of me.  I have to close three
browsers, several file managers plus whatever else I am doing before I
can logout.  Then I have to reopen all that when I log back in.  On top
of that, I have to wait for a download to stop as well.  Yea, it's
annoying, putting it mildly.  lol  I thought if I killed it, it would
take the whole GUI thingy with it .  Since it is still chewing away,
makes me think about the Pacman days, I'll kill that thing in a few
minutes, after closing important stuff first just in case. 

I got the last several lines of sddm.log.  Here it is complete with a WW
in there, about three lines from the bottom. 


[01:32:50.474] (II) DAEMON: Greeter session started successfully
[01:32:50.499] (II) DAEMON: Message received from greeter: Connect
[01:32:57.872] (II) DAEMON: Message received from greeter: Login
[01:32:57.872] (II) DAEMON: Reading from
"/usr/share/xsessions/plasma.desktop"
[01:32:57.872] (II) DAEMON: Reading from
"/usr/share/xsessions/plasma.desktop"
[01:32:57.872] (II) DAEMON: Session
"/usr/share/xsessions/plasma.desktop" selected, command:
"/usr/bin/startplasma-x11"
[01:32:57.948] (II) HELPER: [PAM] Starting...
[01:32:57.948] (II) HELPER: [PAM] Authenticating...
[01:32:57.991] (II) HELPER: [PAM] Preparing to converse...
[01:32:57.991] (II) HELPER: [PAM] Conversation with 1 messages
[01:32:57.997] (II) HELPER: [PAM] returning.
[01:32:58.016] (II) DAEMON: Authenticated successfully
[01:32:58.152] (II) HELPER: [PAM] Closing session
[01:32:58.153] (II) HELPER: [PAM] Ended.
[01:32:58.153] (II) DAEMON: Auth: sddm-helper exited successfully
[01:32:58.153] (II) DAEMON: Greeter stopped.
[01:32:58.225] (II) HELPER: Starting: "/usr/share/sddm/scripts/Xsession
\"/usr/bin/startplasma-x11\""
[01:32:58.225] (WW) HELPER: Could not open stderr to
"/home/dale/.local/share/sddm/xorg-session.log"
[01:32:58.225] (II) HELPER: Adding cookie to "/home/dale/.Xauthority"
[01:32:58.245] (II) DAEMON: Session started
root@fireball / #



So off I go to check into that file.  I get this and change permissions
for the second ls.


root@fireball / # tail /home/dale/.local/share/sddm/xorg-session.log
root@fireball / # ls -al /home/dale/.local/share/sddm/xorg-session.log
-rw------- 1 root root 0 Mar  4  2019
/home/dale/.local/share/sddm/xorg-session.log
root@fireball / # ls -al /home/dale/.local/share/sddm/xorg-session.log
-rw------- 1 dale users 0 Mar  4  2019
/home/dale/.local/share/sddm/xorg-session.log
root@fireball / #


As you can see, the first time it was owned by root, and is empty, which
I bet requires it to be dale:user so I changed it.  I bet it is building
a log and keeping it in memory because it can't access the file to write
it.  I'm going to logout and see what it does.  I'll finish when I get
back.  :-D

OK.  Logged back in and now I get this in the sddm.log.


[10:45:28.213] (II) HELPER: [PAM] Starting...
[10:45:28.213] (II) HELPER: [PAM] Authenticating...
[10:45:28.253] (II) HELPER: [PAM] Preparing to converse...
[10:45:28.253] (II) HELPER: [PAM] Conversation with 1 messages
[10:45:28.259] (II) HELPER: [PAM] returning.
[10:45:28.287] (II) DAEMON: Authenticated successfully
[10:45:28.391] (II) HELPER: Starting: "/usr/share/sddm/scripts/Xsession
\"/usr/bin/startplasma-x11\""
[10:45:28.393] (II) HELPER: Adding cookie to "/home/dale/.Xauthority"
[10:45:28.400] (II) DAEMON: Session started
[10:45:28.416] (II) HELPER: [PAM] Closing session
[10:45:28.417] (II) HELPER: [PAM] Ended.
[10:45:28.418] (II) DAEMON: Auth: sddm-helper exited successfully
[10:45:28.418] (II) DAEMON: Greeter stopped.
root@fireball / #


I don't see any WW lines there.  If I scroll up I can see the original I
posted above but no WW since.  Can we all say a prayer now????  

I bet when I switched to sddm, it didn't change the permissions like it
should and that threw a wrench in the gears.  I'll know for sure in a
few hours.  It chewed through memory real fast after the last login. 
Within just a very few hours, it was over 4GBs.  It seems to stop itself
around that number tho.  I'm not sure what to think about that tho.

I'll post back in a bit.  Give it time to eat some Pacman dots.  I think
you got it tho.  I really hope that was it. 

Dale

:-)  :-) 

P. S. Made eye Doctor appt today.  Maybe this old goat will see better
in a couple months when new glasses come in.  O_O

[-- Attachment #2: Type: text/html, Size: 6370 bytes --]

Re: [gentoo-user] sddm-helper and high memory usage

[J. Roeleveld]

On 20 May 2020 17:56:29 CEST, Dale <rdalek1967@gmail.com> wrote:
>J. Roeleveld wrote:
>>
>> Dale,
>>
>> The few times I have issues with "sddm-helper" is when I resume my
>laptop from 
>> hibernate. (Not always, but occasionally)
>> The issue I see is 100% CPU-usage and a black X-display. I can switch
>to 
>> console (CTRL+ALT+F1), login as root and kill the offending
>sddm-helper.
>> It gets restarted automatically and I see no issue.
>>
>> Do you tend to lock your screen a lot? As it might be related to
>screensavers. 
>> (I have a simple static lock-screen, nothing remotely fancy)
>>
>> Also, you can try killing "kill -9 sddm-helper" when it goes up and
>see what 
>> happens next.
>>
>> Is there anything in the sddm-logs?
>> Mine, for some reason, writes to /var/log/sddm.log
>>
>> Do you have anything special in your Xsession files and/or profiles
>(incl. 
>> bash_profile and bashrc) that is non-default?
>>
>> Which login-theme do you use?
>>
>> --
>> Joost
>
>Well, I didn't know I could kill that thing.  I been logging out and
>back in which annoys the stuffing out of me.  I have to close three
>browsers, several file managers plus whatever else I am doing before I
>can logout.  Then I have to reopen all that when I log back in.  On top
>of that, I have to wait for a download to stop as well.  Yea, it's
>annoying, putting it mildly.  lol  I thought if I killed it, it would
>take the whole GUI thingy with it .  Since it is still chewing away,
>makes me think about the Pacman days, I'll kill that thing in a few
>minutes, after closing important stuff first just in case. 
>
>I got the last several lines of sddm.log.  Here it is complete with a
>WW
>in there, about three lines from the bottom. 
>
>
>[01:32:50.474] (II) DAEMON: Greeter session started successfully
>[01:32:50.499] (II) DAEMON: Message received from greeter: Connect
>[01:32:57.872] (II) DAEMON: Message received from greeter: Login
>[01:32:57.872] (II) DAEMON: Reading from
>"/usr/share/xsessions/plasma.desktop"
>[01:32:57.872] (II) DAEMON: Reading from
>"/usr/share/xsessions/plasma.desktop"
>[01:32:57.872] (II) DAEMON: Session
>"/usr/share/xsessions/plasma.desktop" selected, command:
>"/usr/bin/startplasma-x11"
>[01:32:57.948] (II) HELPER: [PAM] Starting...
>[01:32:57.948] (II) HELPER: [PAM] Authenticating...
>[01:32:57.991] (II) HELPER: [PAM] Preparing to converse...
>[01:32:57.991] (II) HELPER: [PAM] Conversation with 1 messages
>[01:32:57.997] (II) HELPER: [PAM] returning.
>[01:32:58.016] (II) DAEMON: Authenticated successfully
>[01:32:58.152] (II) HELPER: [PAM] Closing session
>[01:32:58.153] (II) HELPER: [PAM] Ended.
>[01:32:58.153] (II) DAEMON: Auth: sddm-helper exited successfully
>[01:32:58.153] (II) DAEMON: Greeter stopped.
>[01:32:58.225] (II) HELPER: Starting: "/usr/share/sddm/scripts/Xsession
>\"/usr/bin/startplasma-x11\""
>[01:32:58.225] (WW) HELPER: Could not open stderr to
>"/home/dale/.local/share/sddm/xorg-session.log"
>[01:32:58.225] (II) HELPER: Adding cookie to "/home/dale/.Xauthority"
>[01:32:58.245] (II) DAEMON: Session started
>root@fireball / #
>
>
>
>So off I go to check into that file.  I get this and change permissions
>for the second ls.
>
>
>root@fireball / # tail /home/dale/.local/share/sddm/xorg-session.log
>root@fireball / # ls -al /home/dale/.local/share/sddm/xorg-session.log
>-rw------- 1 root root 0 Mar  4  2019
>/home/dale/.local/share/sddm/xorg-session.log
>root@fireball / # ls -al /home/dale/.local/share/sddm/xorg-session.log
>-rw------- 1 dale users 0 Mar  4  2019
>/home/dale/.local/share/sddm/xorg-session.log
>root@fireball / #
>
>
>As you can see, the first time it was owned by root, and is empty,
>which
>I bet requires it to be dale:user so I changed it.  I bet it is
>building
>a log and keeping it in memory because it can't access the file to
>write
>it.  I'm going to logout and see what it does.  I'll finish when I get
>back.  :-D
>
>OK.  Logged back in and now I get this in the sddm.log.
>
>
>[10:45:28.213] (II) HELPER: [PAM] Starting...
>[10:45:28.213] (II) HELPER: [PAM] Authenticating...
>[10:45:28.253] (II) HELPER: [PAM] Preparing to converse...
>[10:45:28.253] (II) HELPER: [PAM] Conversation with 1 messages
>[10:45:28.259] (II) HELPER: [PAM] returning.
>[10:45:28.287] (II) DAEMON: Authenticated successfully
>[10:45:28.391] (II) HELPER: Starting: "/usr/share/sddm/scripts/Xsession
>\"/usr/bin/startplasma-x11\""
>[10:45:28.393] (II) HELPER: Adding cookie to "/home/dale/.Xauthority"
>[10:45:28.400] (II) DAEMON: Session started
>[10:45:28.416] (II) HELPER: [PAM] Closing session
>[10:45:28.417] (II) HELPER: [PAM] Ended.
>[10:45:28.418] (II) DAEMON: Auth: sddm-helper exited successfully
>[10:45:28.418] (II) DAEMON: Greeter stopped.
>root@fireball / #
>
>
>I don't see any WW lines there.  If I scroll up I can see the original
>I
>posted above but no WW since.  Can we all say a prayer now????  
>
>I bet when I switched to sddm, it didn't change the permissions like it
>should and that threw a wrench in the gears.  I'll know for sure in a
>few hours.  It chewed through memory real fast after the last login. 
>Within just a very few hours, it was over 4GBs.  It seems to stop
>itself
>around that number tho.  I'm not sure what to think about that tho.
>
>I'll post back in a bit.  Give it time to eat some Pacman dots.  I
>think
>you got it tho.  I really hope that was it. 
>
>Dale
>
>:-)  :-) 
>
>P. S. Made eye Doctor appt today.  Maybe this old goat will see better
>in a couple months when new glasses come in.  O_O

Really quick as on mobile.
Killing "sddm-helper" doesn't kill my session when I do it.
So you might not need to log off either.
Just switch to root and hit it with kill -9 if it misbehaves
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: [gentoo-user] sddm-helper and high memory usage

[Dale]

[-- Attachment #1: Type: text/plain, Size: 6294 bytes --]

J. Roeleveld wrote:
> On 20 May 2020 17:56:29 CEST, Dale <rdalek1967@gmail.com> wrote:
>> J. Roeleveld wrote:
>>> Dale,
>>>
>>> The few times I have issues with "sddm-helper" is when I resume my
>> laptop from 
>>> hibernate. (Not always, but occasionally)
>>> The issue I see is 100% CPU-usage and a black X-display. I can switch
>> to 
>>> console (CTRL+ALT+F1), login as root and kill the offending
>> sddm-helper.
>>> It gets restarted automatically and I see no issue.
>>>
>>> Do you tend to lock your screen a lot? As it might be related to
>> screensavers. 
>>> (I have a simple static lock-screen, nothing remotely fancy)
>>>
>>> Also, you can try killing "kill -9 sddm-helper" when it goes up and
>> see what 
>>> happens next.
>>>
>>> Is there anything in the sddm-logs?
>>> Mine, for some reason, writes to /var/log/sddm.log
>>>
>>> Do you have anything special in your Xsession files and/or profiles
>> (incl. 
>>> bash_profile and bashrc) that is non-default?
>>>
>>> Which login-theme do you use?
>>>
>>> --
>>> Joost
>> Well, I didn't know I could kill that thing.  I been logging out and
>> back in which annoys the stuffing out of me.  I have to close three
>> browsers, several file managers plus whatever else I am doing before I
>> can logout.  Then I have to reopen all that when I log back in.  On top
>> of that, I have to wait for a download to stop as well.  Yea, it's
>> annoying, putting it mildly.  lol  I thought if I killed it, it would
>> take the whole GUI thingy with it .  Since it is still chewing away,
>> makes me think about the Pacman days, I'll kill that thing in a few
>> minutes, after closing important stuff first just in case. 
>>
>> I got the last several lines of sddm.log.  Here it is complete with a
>> WW
>> in there, about three lines from the bottom. 
>>
>>
>> [01:32:50.474] (II) DAEMON: Greeter session started successfully
>> [01:32:50.499] (II) DAEMON: Message received from greeter: Connect
>> [01:32:57.872] (II) DAEMON: Message received from greeter: Login
>> [01:32:57.872] (II) DAEMON: Reading from
>> "/usr/share/xsessions/plasma.desktop"
>> [01:32:57.872] (II) DAEMON: Reading from
>> "/usr/share/xsessions/plasma.desktop"
>> [01:32:57.872] (II) DAEMON: Session
>> "/usr/share/xsessions/plasma.desktop" selected, command:
>> "/usr/bin/startplasma-x11"
>> [01:32:57.948] (II) HELPER: [PAM] Starting...
>> [01:32:57.948] (II) HELPER: [PAM] Authenticating...
>> [01:32:57.991] (II) HELPER: [PAM] Preparing to converse...
>> [01:32:57.991] (II) HELPER: [PAM] Conversation with 1 messages
>> [01:32:57.997] (II) HELPER: [PAM] returning.
>> [01:32:58.016] (II) DAEMON: Authenticated successfully
>> [01:32:58.152] (II) HELPER: [PAM] Closing session
>> [01:32:58.153] (II) HELPER: [PAM] Ended.
>> [01:32:58.153] (II) DAEMON: Auth: sddm-helper exited successfully
>> [01:32:58.153] (II) DAEMON: Greeter stopped.
>> [01:32:58.225] (II) HELPER: Starting: "/usr/share/sddm/scripts/Xsession
>> \"/usr/bin/startplasma-x11\""
>> [01:32:58.225] (WW) HELPER: Could not open stderr to
>> "/home/dale/.local/share/sddm/xorg-session.log"
>> [01:32:58.225] (II) HELPER: Adding cookie to "/home/dale/.Xauthority"
>> [01:32:58.245] (II) DAEMON: Session started
>> root@fireball / #
>>
>>
>>
>> So off I go to check into that file.  I get this and change permissions
>> for the second ls.
>>
>>
>> root@fireball / # tail /home/dale/.local/share/sddm/xorg-session.log
>> root@fireball / # ls -al /home/dale/.local/share/sddm/xorg-session.log
>> -rw------- 1 root root 0 Mar  4  2019
>> /home/dale/.local/share/sddm/xorg-session.log
>> root@fireball / # ls -al /home/dale/.local/share/sddm/xorg-session.log
>> -rw------- 1 dale users 0 Mar  4  2019
>> /home/dale/.local/share/sddm/xorg-session.log
>> root@fireball / #
>>
>>
>> As you can see, the first time it was owned by root, and is empty,
>> which
>> I bet requires it to be dale:user so I changed it.  I bet it is
>> building
>> a log and keeping it in memory because it can't access the file to
>> write
>> it.  I'm going to logout and see what it does.  I'll finish when I get
>> back.  :-D
>>
>> OK.  Logged back in and now I get this in the sddm.log.
>>
>>
>> [10:45:28.213] (II) HELPER: [PAM] Starting...
>> [10:45:28.213] (II) HELPER: [PAM] Authenticating...
>> [10:45:28.253] (II) HELPER: [PAM] Preparing to converse...
>> [10:45:28.253] (II) HELPER: [PAM] Conversation with 1 messages
>> [10:45:28.259] (II) HELPER: [PAM] returning.
>> [10:45:28.287] (II) DAEMON: Authenticated successfully
>> [10:45:28.391] (II) HELPER: Starting: "/usr/share/sddm/scripts/Xsession
>> \"/usr/bin/startplasma-x11\""
>> [10:45:28.393] (II) HELPER: Adding cookie to "/home/dale/.Xauthority"
>> [10:45:28.400] (II) DAEMON: Session started
>> [10:45:28.416] (II) HELPER: [PAM] Closing session
>> [10:45:28.417] (II) HELPER: [PAM] Ended.
>> [10:45:28.418] (II) DAEMON: Auth: sddm-helper exited successfully
>> [10:45:28.418] (II) DAEMON: Greeter stopped.
>> root@fireball / #
>>
>>
>> I don't see any WW lines there.  If I scroll up I can see the original
>> I
>> posted above but no WW since.  Can we all say a prayer now????  
>>
>> I bet when I switched to sddm, it didn't change the permissions like it
>> should and that threw a wrench in the gears.  I'll know for sure in a
>> few hours.  It chewed through memory real fast after the last login. 
>> Within just a very few hours, it was over 4GBs.  It seems to stop
>> itself
>> around that number tho.  I'm not sure what to think about that tho.
>>
>> I'll post back in a bit.  Give it time to eat some Pacman dots.  I
>> think
>> you got it tho.  I really hope that was it. 
>>
>> Dale
>>
>> :-)  :-) 
>>
>> P. S. Made eye Doctor appt today.  Maybe this old goat will see better
>> in a couple months when new glasses come in.  O_O
> Really quick as on mobile.
> Killing "sddm-helper" doesn't kill my session when I do it.
> So you might not need to log off either.
> Just switch to root and hit it with kill -9 if it misbehaves


Next time, that's the plan.  So far tho, it is working fine.  This is
what ps shows:

root     23338  0.0  0.0  54528 14400

It hasn't changed since I logged in.  It's hasn't increased even one
byte.  Usually by now it would be up to a few 100MBs or so. 

Dale

:-)  :-) 

[-- Attachment #2: Type: text/html, Size: 7289 bytes --]

Re: [gentoo-user] SOLVED sddm-helper and high memory usage

[Dale]

Dale wrote:
>
>
> Next time, that's the plan.  So far tho, it is working fine.  This is
> what ps shows:
>
> root     23338  0.0  0.0  54528 14400
>
> It hasn't changed since I logged in.  It's hasn't increased even one
> byte.  Usually by now it would be up to a few 100MBs or so. 
>
> Dale
>
> :-)  :-) 


It's been several hours now.  Usually by now it would be well over a
Gigabyte and more recently even more than that.  So, no logging out and
back in or anything and here is where it is sitting at now. 


root     23338  0.0  0.0  54528 14400


It would appear that it is fixed.  It hasn't changed by even the
smallest amount.  It hasn't changed at all. 

< Dale does a little dance >

Thanks Joost.  You sending me to the sddm.log lead to the fix.  I have
no idea how the permissions got set wrong on the file tho.  I didn't
even know it existed.

Dale

:-)  :-)

Re: [gentoo-user] SOLVED sddm-helper and high memory usage

[J. Roeleveld]

On 21 May 2020 02:54:44 CEST, Dale <rdalek1967@gmail.com> wrote:
>Dale wrote:
>>
>>
>> Next time, that's the plan.  So far tho, it is working fine.  This is
>> what ps shows:
>>
>> root     23338  0.0  0.0  54528 14400
>>
>> It hasn't changed since I logged in.  It's hasn't increased even one
>> byte.  Usually by now it would be up to a few 100MBs or so. 
>>
>> Dale
>>
>> :-)  :-) 
>
>
>It's been several hours now.  Usually by now it would be well over a
>Gigabyte and more recently even more than that.  So, no logging out and
>back in or anything and here is where it is sitting at now. 
>
>
>root     23338  0.0  0.0  54528 14400
>
>
>It would appear that it is fixed.  It hasn't changed by even the
>smallest amount.  It hasn't changed at all. 
>
>< Dale does a little dance >
>
>Thanks Joost.  You sending me to the sddm.log lead to the fix.  I have
>no idea how the permissions got set wrong on the file tho.  I didn't
>even know it existed.
>
>Dale
>
>:-)  :-)

You're welcome.
I didn't know about a logfile buried inside the hone directory either and that is not something I am happy with.

Will be something I need to look into and hopefully change.

--
Joost
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: [gentoo-user] sddm-helper and high memory usage

[Peter Humphrey]

On Wednesday, 20 May 2020 16:56:29 BST Dale wrote:

> Well, I didn't know I could kill that thing.  I been logging out and
> back in which annoys the stuffing out of me.  I have to close three
> browsers, several file managers plus whatever else I am doing before I
> can logout.  Then I have to reopen all that when I log back in.

Why do you have to do that yourself? I'd have thought that sddm would take 
care of it for you. It does for me.

> On top of that, I have to wait for a download to stop as well.  Yea, it's
> annoying, putting it mildly.  lol  I thought if I killed it, it would
> take the whole GUI thingy with it .  Since it is still chewing away,
> makes me think about the Pacman days, I'll kill that thing in a few
> minutes, after closing important stuff first just in case. 

Whenever an update changes a lot of GUI stuff I drop to a VT and tell it "/etc/
init.d/xdm restart && logout". That ought to be equivalent to killing sddm but 
kinder.

-- 
Regards,
Peter.

Re: [gentoo-user] sddm-helper and high memory usage

[Dale]

[-- Attachment #1: Type: text/plain, Size: 1952 bytes --]

Peter Humphrey wrote:
> On Wednesday, 20 May 2020 16:56:29 BST Dale wrote:
>
>> Well, I didn't know I could kill that thing.  I been logging out and
>> back in which annoys the stuffing out of me.  I have to close three
>> browsers, several file managers plus whatever else I am doing before I
>> can logout.  Then I have to reopen all that when I log back in.
> Why do you have to do that yourself? I'd have thought that sddm would take 
> care of it for you. It does for me.

I have a saved session but if I restart everything at once, my internet
chokes and some tabs fail to load.  So, I have the basic stuff in a
saved session but still have to do some myself.  Of course I close stuff
before logging out just to be safe. 


>> On top of that, I have to wait for a download to stop as well.  Yea, it's
>> annoying, putting it mildly.  lol  I thought if I killed it, it would
>> take the whole GUI thingy with it .  Since it is still chewing away,
>> makes me think about the Pacman days, I'll kill that thing in a few
>> minutes, after closing important stuff first just in case. 
> Whenever an update changes a lot of GUI stuff I drop to a VT and tell it "/etc/
> init.d/xdm restart && logout". That ought to be equivalent to killing sddm but 
> kinder.
>


In this case, just logging out and right back in works.  The first time
I did it, I switched to a terminal and checked after logging out.  The
memory sddm was using was already down to almost nothing.  I knew then
that logging out and right back in was enough.  It only takes a few
seconds to log out and back in but it is annoying because at times, I
may have 40 tabs open.  Those have to reload as well which with my DSL,
takes a while. 

After a update, especially a KDE or qt update, I logout and go to boot
runlevel and back.  That restarts everything KDE plus others that may
need restarting as well.  I find some stuff is real touchy after updates. 

Dale

:-)  :-) 

[-- Attachment #2: Type: text/html, Size: 2710 bytes --]