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] Firefox, Seamonkey to if I can, and memory limits.
Date: Sun, 1 Sep 2024 09:24:46 -0500	[thread overview]
Message-ID: <f4b96a32-fa64-107d-474a-f3699933d6b7@gmail.com> (raw)
In-Reply-To: <428b05d4-0828-45f2-add6-48123ba9073e@youngman.org.uk>

Wols Lists wrote:
> On 31/08/2024 19:39, Dale wrote:
>> I did a lot of searching and almost all of it relates to using cgroups
>> for services, like mysql or something.  I haven't found anything that
>> explains how to do it for a program started by a user.  It may be doable
>> but I've yet to find it.
>
> I did a quick search and found this ...
>
> https://unix.stackexchange.com/questions/555080/using-cgroup-to-limit-program-memory-as-its-running
>
>
> reading through it, it appears to tell you (a) how to set up the
> cgroup, (b) how to put a running program into a cgroup, and (c) (most
> importantly) how to start a program in a cgroup.
>
> So what you'd do is create the cgroup, then edit the firefox and
> seamonkey desktop files to use cgexec to start them.
>
> Beyond that tip, you're on your own but it looks promising. I've not
> done it, so I don't know ...
>
> Cheers,
> Wol
>
>


It looks like I do need to do this.  Firefox just went nuts on memory
again.  One of my Firefox profiles was using 98% of memory. 

From that link, it looks like that is done manually.  In other words,
when I start Firefox, I have to add the process to the cgroup by hand. 
Shouldn't there be a way to do it automatically?  Like add it to the
command that runs the program name in the application menu? 

I did see where a lot of services are listed in the directory mentioned
in link tho.  I also found out elsewhere that I have to enable more
cgroup controls in the kernel.  I did that the other day.  I just need
to reboot now.  Once I reboot and those extra drivers are working, I can
peek at things.  See how it is done with other things. 

For something that is designed to do this sort of thing, why is it so
hard to find docs for how to do it?  I've read of other people having
Firefox and other programs go nuts on memory before.  I can't be the
only one who wants to set limits on a process like this.  :/ 

Thanks.  If you find anything else, let me know. 

Dale

:-)  :-) 


  reply	other threads:[~2024-09-01 14:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-23 18:38 [gentoo-user] Firefox, Seamonkey to if I can, and memory limits Dale
2024-08-23 21:22 ` Wol
2024-08-23 23:03   ` Matt Jolly
2024-08-24  0:42     ` Dale
2024-08-24  4:25       ` Matt Jolly
2024-08-24  8:30       ` Walter Dnes
2024-08-25 15:20         ` Dale
2024-08-31 17:32           ` Michael
2024-08-31 18:39             ` Dale
2024-09-01  9:35               ` Wols Lists
2024-09-01 14:24                 ` Dale [this message]
2024-09-01 19:08                   ` Wols Lists
2024-09-01 19:36                     ` Dale
2024-09-01 20:45                       ` Wol
2024-09-01 21:36                         ` Dale
2024-09-02  6:49                           ` Wols Lists
2024-08-24  9:15     ` Wol

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=f4b96a32-fa64-107d-474a-f3699933d6b7@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