From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Firefox, Seamonkey to if I can, and memory limits.
Date: Sat, 31 Aug 2024 18:32:47 +0100 [thread overview]
Message-ID: <9330460.CDJkKcVGEf@rogueboard> (raw)
In-Reply-To: <6442a869-f24c-5fc7-ef03-34b01bd85dcb@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1708 bytes --]
On Sunday, 25 August 2024 16:20:19 BST Dale wrote:
> Walter Dnes wrote:
> > On Fri, Aug 23, 2024 at 07:42:05PM -0500, Dale wrote
> >
> >> I still use openrc. I'll look around and see what I can find. Now I
> >> know what to look for. Thing is, not sure I use cgroups either, unless
> >> it is on by default. o_O
> >>
> > The bottom half of file /etc/rc.conf is devoted to cgroups settings.
> >
> > Look for the line...
> > # LINUX CGROUPS RESOURCE MANAGEMENT
>
> I have searched for info on this. I did find the settings in rc.conf.
> I see a lot of discussion about running services, like cups, mysql and
> such, and controlling them. What I don't see is how to set up a regular
> program like Firefox or any other program that a user runs directly. I
> suspect it can be done but I can't find a howto that shows how to do it.
>
> I'll keep digging but if anyone has a link they have ran up on before
> and would like to share, it would be nice. It seems what I want to do
> is not very common. Thing is, Firefox sometimes goes nuts and when it
> does, it is determined to crash my system if I don't catch it. Even if
> I had the full 128GBs, it would just take longer to consume it as well.
> The best way I see to deal with this, limit its access to memory. It
> seems there is a tool to do this, now to figure out how to use it.
>
> Thanks to all for the help.
>
> Dale
>
> :-) :-)
I have not dived into cgroups in any big way. I would think setting up a
dekstop application with many complicated & complex userspace dependencies is
not a simple task.
Perhaps a way to approach this is by launching firefox as a different user and
setting a memory limit for that user.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-08-31 17:32 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 [this message]
2024-08-31 18:39 ` Dale
2024-09-01 9:35 ` Wols Lists
2024-09-01 14:24 ` Dale
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=9330460.CDJkKcVGEf@rogueboard \
--to=confabulate@kintzios.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