Re: FIREFOX is killing the whole PC Part III

[hede]

On 23.11.2022 17:09, Schwibinger Michael wrote:
> Good afternoon
> 
>  I saw cgroups.
> 
>  Thank You.
> 
>  But I cant understand.
> 
>  Is it a concept to limit all tasks?

You can limit all, a single one or (the name suggests this one) a group of 
processes. There are plenty of system resources which can be configured. 

>  Where can I find a introduction?

I don't know either. But maybe this one is fine to start with:

https://www.redhat.com/sysadmin/cgroups-part-one

Some examples limiting Firefox to 500 MB of RAM and low CPU resources, do as 
root:



# cd into the cgroup filesystem, defaults to cgroup2 on Debian Bullseye, others 
may vary
cd /sys/fs/cgroup/

# create a new cgroup
mkdir ffox

# cd into the cgroup dir
cd ffox/

# add all firefox-esr processes to the cgroup, all newly created subprocesses 
will automatically get added to ffox cgroup
for i in $(pidof firefox-esr); do echo $i > cgroup.procs ; done

# limit memory usage to 500 MB
echo 500M > memory.high 

# limit cpu usage to less wight (defaults to 100)
echo 10 >  cpu.weight

# also limit swap memory because else it will fill swap after the memory limit 
kicks in
echo 100M > memory.swap.max 



... now watch Firefox stall if other processes either use CPU resources or 
Firefox tries to consume more than 600 MB of Memory (which is small nowadays 
for multiple tabs; but mind, if Firefox already has more memory allocated it 
will keep this). 

Typically you can use some more friendly userspace interface. But don't think 
of using cgroup-tools with Debian Bullseye: Version 0.41 in Bullseyes 
repository supports cgroups V1 only while Bullseyes Kernel defaults to V2.

There's plenty of help you can find with your favourite Internet search engine. 

regards
hede


PS: to remove Firefox from the ffox cgroup either restart Firefox or:

cd /sys/fs/cgroup/ffox/ && for i in $(cat cgroup.procs); do echo $i > 
../cgroup.procs ; done 

AW: FIREFOX is killing the whole PC PART II

[Schwibinger Michael]

I ll print it out
and try it.

Thank Yiu
Regards
Sope


We do clean cache once a week.




Von: Gareth Evans 
Gesendet: Montag, 21. November 2022 07:04
An: debian-user@lists.debian.org 
Betreff: Re: FIREFOX is killing the whole PC PART II

On Mon 21 Nov 2022, at 06:56, Gareth Evans  wrote:
> On Sun 20 Nov 2022, at 10:53, Schwibinger Michael  wrote:
>> Hello
>> and thank You.
>>
>>
>>
>>
>> Thank you, this did help.
>
>> Two Questions more.
>
>> How can I find by terminal all dirt which is produced by browsers (Chrome, 
>> Firefox, Midori ...)?
>> I did try something like cache, but there were no new files.
>
> I think it would be easier to clear the cache and other data (possibly
> including history if you wish) automatically when the browsers close.
> There are usually settings available to do that.
>
> See below.
>
>> How can I tell the browser (Firefox, Chrome and so on): Do not save any 
>> information.
>> Example:
>> I do open www.hotmail.de<http://www.hotmail.de>, sending Emails, and close 
>> hotmail.
>> No there should be no information left on the pc abour hotmail. Only the 
>> bookmark www.hotmail.de<http://www.hotmail.de>.
>
> If you mean an actual bookmark, clearing the history will not remove this.
>

> For Firefox:
>
> Settings > Privacy and Security
>
> - Delete cookies and site data when Firefox is closed
>
> - History

Make sure "Firefox will: Use custom settings for history" is selected, to see 
further options

Re: FIREFOX is killing the whole PC PART II

[Cindy Sue Causey]

> Von: Gareth Evans 
> Gesendet: Montag, 21. November 2022 06:56
> An: debian-user@lists.debian.org 
> Betreff: Re: FIREFOX is killing the whole PC PART II
>
> So there seem to be two ways to clear cookies and site data when closing
> Firefox, but I'm not sure if the options under History > Settings include
> all the "site data" removed by the other setting.
>
> Best wishes,
> Gareth


What about creating a regularly running script to clear those out?
I've thought about that myself for the very reason of browser slowdown
but never followed through on the idea. Anacron is coming to mind
because it just suffered a glitch where the scripts silently didn't
run after a recent upgrade. That's how I know what it does to then
offer it as a suggestion. :D

Cindy :)
-- 
Talking Rock, Pickens County, Georgia, USA
* runs with birdseed *

Re: FIREFOX is killing the whole PC PART II

[Cindy Sue Causey]

On 11/21/22, Gareth Evans  wrote:
> On Sun 20 Nov 2022, at 10:53, Schwibinger Michael  wrote:
>
>> How can I find by terminal all dirt which is produced by browsers (Chrome,
>> Firefox, Midori ...)?
>> I did try something like cache, but there were no new files.
>
> I think it would be easier to clear the cache and other data (possibly
> including history if you wish) automatically when the browsers close.  There
> are usually settings available to do that.


Speaking of settings and previous mentions of possible concerns about
what tabs appear on startup, there's also a setting
(about:preferences) for declaring what appears upon startup. These
days, it's fairly normal to see something similar to "Open previous
windows and tabs", open with a blank page, and open with a personal
favorite webpage.

That said, I'm only seeing the "Open previous windows" selection. That
makes a user feel like the browser is maybe getting paid to
alternatively provide potentially sponsored content with no
immediately visible "Off" button..

Maybe.

Or not.

Cindy :)
-- 
Talking Rock, Pickens County, Georgia, USA
* runs with birdseed *

AW: AW: FIREFOX is killing the whole PC Part III

[Schwibinger Michael]

I ll print it out
and I ll try it.

Thank Yu

Sophie



Von: Curt 
Gesendet: Sonntag, 20. November 2022 20:46
An: debian-user@lists.debian.org 
Betreff: Re: AW: FIREFOX is killing the whole PC Part III

On 2022-11-20, Schwibinger Michael  wrote:
>
> To avoid problems by surfing
> I tried
> nice.
> No good enough.
>
> I did try
>
> nice -n 19 chromium-browser
>  cpulimit -e chrome -l 30
>
> But this also did not work,
> cause URLS do open other URLs.
>
> I found this.
>
> 2 Questions:
>
> What does it do?
>
> Why does it not work.
>
>
> # Find and limit all child processes of all browsers.
> for name in firefox firefox-esr chromium chrome
> do
> for ppid in $(pgrep "$name")
> do
> cpulimit --pid="$ppid" --limit"$LIMIT" &
> for pid in "$ppid" $(pgrep --parent "$ppid")
> do
> cpulimit --pid="$pid" --limit"$LIMIT" &
> done
> done
> done
>
> Regards Sophie

I suppose it does what it says in the comment at the front, and fails to
work because you need to define $LIMIT beforehand.

  -l, --limit=N
 percentage  of  CPU allowed from 1 up. Usually 1 - 100,
 but can be higher on multi-core CPUs. (mandatory)


  # cpulimit -l 20 firefox
 Launch Firefox web browser and limit its CPU usage to
 20%

AW: FIREFOX is killing the whole PC PART II

[Schwibinger Michael]

Thank You.

I ll do it.

Regards

Von: Bret Busby 
Gesendet: Montag, 21. November 2022 07:43
An: debian-user@lists.debian.org 
Betreff: Re: FIREFOX is killing the whole PC PART II

On 21/11/2022 14:56, Gareth Evans wrote:
> On Sun 20 Nov 2022, at 10:53, Schwibinger Michael  wrote:
>> Hello
>> and thank You.
>>
>>
>>
>>
>> Thank you, this did help.
>
>> Two Questions more.
>
>> How can I find by terminal all dirt which is produced by browsers (Chrome, 
>> Firefox, Midori ...)?
>> I did try something like cache, but there were no new files.
>
> I think it would be easier to clear the cache and other data (possibly 
> including history if you wish) automatically when the browsers close.  There 
> are usually settings available to do that.
>
> See below.
>
>> How can I tell the browser (Firefox, Chrome and so on): Do not save any 
>> information.
>> Example:
>> I do open www.hotmail.de<http://www.hotmail.de>, sending Emails, and close 
>> hotmail.
>> No there should be no information left on the pc abour hotmail. Only the 
>> bookmark www.hotmail.de<http://www.hotmail.de>.
>
> If you mean an actual bookmark, clearing the history will not remove this.
>
> For Firefox:
>
> Settings > Privacy and Security
>
> - Delete cookies and site data when Firefox is closed
>
> - History
> -- Clear history when Firefox closes [Settings...]
>
> There are options for what to clear if you click the "settings" button, such 
> as
>
> - browsing history
> - cookies
> - cache
>
> So there seem to be two ways to clear cookies and site data when closing 
> Firefox, but I'm not sure if the options under History > Settings include all 
> the "site data" removed by the other setting.
>
> Best wishes,
> Gareth
>
>
>
>>
>>
>> Thank you.
>>
>>
>> Reards,
>> Sophie
>>
>>
>>
>> *Von:* Gareth Evans 
>> *Gesendet:* Samstag, 19. November 2022 14:12
>> *An:* debian-user@lists.debian.org 
>> *Betreff:* Re: FIREFOX is killing the whole PC
>>
>> On Sat 19 Nov 2022, at 13:14, DdB  
>> wrote:
>>> Am 19.11.2022 um 10:34 schrieb Schwibinger Michael:
>>>> Hello
>>>>
>>>> Any idea?
>>>>
>>>> What did happen?
>>>> FF did open a page with bad PC,
>>>> so it needs 5 minutes to open it.
>>>> We killed the tab.
>>>> When we now try to open FF
>>>> whole PC is blocked.
>>>> How can we clean FF
>>>> because bad page is in it.
>>>>
>>>> Regards
>>>> Sophie
>>>>
>>
>>> Did you try to start it from the commandline with the option safe-mode?
>>>
>>> firefox --safe-mode
>>
>> If the idea is to prevent previous tabs from opening on startup, that only 
>> works for me if firefox is already running when I run
>>
>> firefox --safe-mode
>>
>> ...which may not be possible for Sophie.
>>
>> Removing the line:
>>
>> user_pref("browser.startup.page", 3);
>>
>> from
>>
>> /home/username/.mozilla/firefox/XXX.default-esr/prefs.js
>>
>> has the desired effect (where "XXX" is the appropriate string of letters and 
>> numbers).
>>
>> There may be more than one such profile directory, in which case, if other 
>> users don't rely on tabs being restored, then remove that line from all the
>>
>> XXX.whatever/prefs.js
>>
>> files you can find.
>>
>> It may also be necessary to add the line
>>
>> user_pref("browser.sessionstore.resume_from_crash", false);
>>
>> I don't know if the order of lines matters.  In my prefs.js, this appears in 
>> the sequence
>>
>> user_pref("browser.search.region", "GB");
>> user_pref("browser.search.widget.inNavBar", true);
>> user_pref("browser.sessionstore.resume_from_crash", false);
>>
>> when added from about:config, but the 2nd line is non-default as well as the 
>> 3rd, and these are only present if added manually or set in settings or 
>> about:config, as appropriate.
>>
>> Hope that helps
>> Gareth
>>
>>
>>
>


You may also want to, in the context of your problem and what you seek, to
1.
(1) set Settings -> Privacy and Security -> Browser Privacy to Strict or
Custom, and
(2) view and consider the Cookies and Site Data settings, and,
(3) the History settings there, and,
(4) in Security, make sure that each of
Block dangerous and deceptive content
Block dangerous downloads
Warn you about unwanted and uncommon software,
is selected

and
2. In Tools -> Add-ons and Themes, search for, and install Bluhell
Firewall. If I find a URL to be blocked by that, if, and, only if, I
sufficiently trust the URL, I then open the URL in the Pale Moon web
browser, where I have, amongst other things, an ad-blocker installed.


..
Bret Busby
Armadale
West Australia
(UTC+0800)
..

AW: AW: FIREFOX is killing the whole PC Part III

[Schwibinger Michael]

Good afternoon

I saw cgroups.

Thank You.

But I cant understand.

Is it a concept to limit all tasks?

Where can I find a introduction?

Regards Sophie




Von: hede 
Gesendet: Montag, 21. November 2022 08:21
An: Debian User 
Betreff: Re: AW: FIREFOX is killing the whole PC Part III

Am 20.11.2022 12:06, schrieb Schwibinger Michael:
> To avoid problems by surfing
> I tried
> nice.
> No good enough.
>
> I did try
>
> nice -n 19 chromium-browser
>  cpulimit -e chrome -l 30
>
> But this also did not work,
> cause URLS do open other URLs.
>
> I found this.
>
> 2 Questions:
>
> What does it do?
>
> Why does it not work.
>
> # Find and limit all child processes of all browsers.
> for name in firefox firefox-esr chromium chrome
> do
> for ppid in $(pgrep "$name")
> do
> cpulimit --pid="$ppid" --limit="$LIMIT" &
> for pid in "$ppid" $(pgrep --parent "$ppid")
> do
> cpulimit --pid="$pid" --limit="$LIMIT" &
> done
> done
> done

(sorry I have not read the whole thread but as some hint for this
specific task:)

Probably the best solution may work on cgroups, limiting not only single
processes but groups of processes, including subprocesses created later
on. This way it's possible not only to limit several processes to some
value for their own but to have several processes combined not to exceed
a limit.

For example if all firefox processes share a cgroup which is limited to
512 cpu.shares, while all other processes in the system have their
default 1024 cpu.shares, firefox (in a whole, with all subprocesses)
will be limited to ~30% CPU time if any other task wants to access the
CPU.

But ad-hoc I do not have a working command example (cgcreate, cgset,
cgexec, ...).

hede

WG: FIREFOX is killing the whole PC PART II

[Schwibinger Michael]

Von: Schwibinger Michael 
Gesendet: Mittwoch, 23. November 2022 16:00
An: Gareth Evans 
Betreff: AW: FIREFOX is killing the whole PC PART II

I ll print it out
and then I ll try it.

Thank You

Regards

Sophie




Von: Gareth Evans 
Gesendet: Montag, 21. November 2022 06:56
An: debian-user@lists.debian.org 
Betreff: Re: FIREFOX is killing the whole PC PART II

On Sun 20 Nov 2022, at 10:53, Schwibinger Michael  wrote:
> Hello
> and thank You.
>
>
>
>
> Thank you, this did help.

> Two Questions more.

> How can I find by terminal all dirt which is produced by browsers (Chrome, 
> Firefox, Midori ...)?
> I did try something like cache, but there were no new files.

I think it would be easier to clear the cache and other data (possibly 
including history if you wish) automatically when the browsers close.  There 
are usually settings available to do that.

See below.

> How can I tell the browser (Firefox, Chrome and so on): Do not save any 
> information.
> Example:
> I do open www.hotmail.de<http://www.hotmail.de>, sending Emails, and close 
> hotmail.
> No there should be no information left on the pc abour hotmail. Only the 
> bookmark www.hotmail.de<http://www.hotmail.de>.

If you mean an actual bookmark, clearing the history will not remove this.

For Firefox:

Settings > Privacy and Security

- Delete cookies and site data when Firefox is closed

- History
-- Clear history when Firefox closes [Settings...]

There are options for what to clear if you click the "settings" button, such as

- browsing history
- cookies
- cache

So there seem to be two ways to clear cookies and site data when closing 
Firefox, but I'm not sure if the options under History > Settings include all 
the "site data" removed by the other setting.

Best wishes,
Gareth



>
>
> Thank you.
>
>
> Reards,
> Sophie
>
>
>
> *Von:* Gareth Evans 
> *Gesendet:* Samstag, 19. November 2022 14:12
> *An:* debian-user@lists.debian.org 
> *Betreff:* Re: FIREFOX is killing the whole PC
>
> On Sat 19 Nov 2022, at 13:14, DdB  
> wrote:
> > Am 19.11.2022 um 10:34 schrieb Schwibinger Michael:
> >> Hello
> >>
> >> Any idea?
> >>
> >> What did happen?
> >> FF did open a page with bad PC,
> >> so it needs 5 minutes to open it.
> >> We killed the tab.
> >> When we now try to open FF
> >> whole PC is blocked.
> >> How can we clean FF
> >> because bad page is in it.
> >>
> >> Regards
> >> Sophie
> >>
>
> > Did you try to start it from the commandline with the option safe-mode?
> >
> > firefox --safe-mode
>
> If the idea is to prevent previous tabs from opening on startup, that only 
> works for me if firefox is already running when I run
>
> firefox --safe-mode
>
> ...which may not be possible for Sophie.
>
> Removing the line:
>
> user_pref("browser.startup.page", 3);
>
> from
>
> /home/username/.mozilla/firefox/XXX.default-esr/prefs.js
>
> has the desired effect (where "XXX" is the appropriate string of letters and 
> numbers).
>
> There may be more than one such profile directory, in which case, if other 
> users don't rely on tabs being restored, then remove that line from all the
>
> XXX.whatever/prefs.js
>
> files you can find.
>
> It may also be necessary to add the line
>
> user_pref("browser.sessionstore.resume_from_crash", false);
>
> I don't know if the order of lines matters.  In my prefs.js, this appears in 
> the sequence
>
> user_pref("browser.search.region", "GB");
> user_pref("browser.search.widget.inNavBar", true);
> user_pref("browser.sessionstore.resume_from_crash", false);
>
> when added from about:config, but the 2nd line is non-default as well as the 
> 3rd, and these are only present if added manually or set in settings or 
> about:config, as appropriate.
>
> Hope that helps
> Gareth
>
>
>

Re: AW: FIREFOX is killing the whole PC Part III

[hede]

Am 20.11.2022 12:06, schrieb Schwibinger Michael:

To avoid problems by surfing
I tried
nice.
No good enough.

I did try

nice -n 19 chromium-browser
 cpulimit -e chrome -l 30

But this also did not work,
cause URLS do open other URLs.

I found this.

2 Questions:

What does it do?

Why does it not work.

# Find and limit all child processes of all browsers.
for name in firefox firefox-esr chromium chrome
do
for ppid in $(pgrep "$name")
do
cpulimit --pid="$ppid" --limit="$LIMIT" &
for pid in "$ppid" $(pgrep --parent "$ppid")
do
cpulimit --pid="$pid" --limit="$LIMIT" &
done
done
done


(sorry I have not read the whole thread but as some hint for this 
specific task:)


Probably the best solution may work on cgroups, limiting not only single 
processes but groups of processes, including subprocesses created later 
on. This way it's possible not only to limit several processes to some 
value for their own but to have several processes combined not to exceed 
a limit.


For example if all firefox processes share a cgroup which is limited to 
512 cpu.shares, while all other processes in the system have their 
default 1024 cpu.shares, firefox (in a whole, with all subprocesses) 
will be limited to ~30% CPU time if any other task wants to access the 
CPU.


But ad-hoc I do not have a working command example (cgcreate, cgset, 
cgexec, ...).


hede

Re: FIREFOX is killing the whole PC PART II

[Bret Busby]

On 21/11/2022 14:56, Gareth Evans wrote:

On Sun 20 Nov 2022, at 10:53, Schwibinger Michael  wrote:

Hello
and thank You.




Thank you, this did help.



Two Questions more.



How can I find by terminal all dirt which is produced by browsers (Chrome, 
Firefox, Midori ...)?
I did try something like cache, but there were no new files.


I think it would be easier to clear the cache and other data (possibly 
including history if you wish) automatically when the browsers close.  There 
are usually settings available to do that.

See below.


How can I tell the browser (Firefox, Chrome and so on): Do not save any 
information.
Example:
I do open www.hotmail.de, sending Emails, and close hotmail.
No there should be no information left on the pc abour hotmail. Only the 
bookmark www.hotmail.de.


If you mean an actual bookmark, clearing the history will not remove this.

For Firefox:

Settings > Privacy and Security

- Delete cookies and site data when Firefox is closed

- History
-- Clear history when Firefox closes [Settings...]

There are options for what to clear if you click the "settings" button, such as

- browsing history
- cookies
- cache

So there seem to be two ways to clear cookies and site data when closing Firefox, but I'm 
not sure if the options under History > Settings include all the "site data" 
removed by the other setting.

Best wishes,
Gareth






Thank you.


Reards,
Sophie



*Von:* Gareth Evans 
*Gesendet:* Samstag, 19. November 2022 14:12
*An:* debian-user@lists.debian.org 
*Betreff:* Re: FIREFOX is killing the whole PC
  
On Sat 19 Nov 2022, at 13:14, DdB  wrote:

Am 19.11.2022 um 10:34 schrieb Schwibinger Michael:

Hello

Any idea?

What did happen?
FF did open a page with bad PC,
so it needs 5 minutes to open it.
We killed the tab.
When we now try to open FF
whole PC is blocked.
How can we clean FF
because bad page is in it.

Regards
Sophie




Did you try to start it from the commandline with the option safe-mode?

firefox --safe-mode


If the idea is to prevent previous tabs from opening on startup, that only 
works for me if firefox is already running when I run

firefox --safe-mode

...which may not be possible for Sophie.

Removing the line:

user_pref("browser.startup.page", 3);

from

/home/username/.mozilla/firefox/XXX.default-esr/prefs.js

has the desired effect (where "XXX" is the appropriate string of letters and 
numbers).

There may be more than one such profile directory, in which case, if other 
users don't rely on tabs being restored, then remove that line from all the

XXX.whatever/prefs.js

files you can find.

It may also be necessary to add the line

user_pref("browser.sessionstore.resume_from_crash", false);

I don't know if the order of lines matters.  In my prefs.js, this appears in 
the sequence

user_pref("browser.search.region", "GB");
user_pref("browser.search.widget.inNavBar", true);
user_pref("browser.sessionstore.resume_from_crash", false);

when added from about:config, but the 2nd line is non-default as well as the 
3rd, and these are only present if added manually or set in settings or 
about:config, as appropriate.

Hope that helps
Gareth








You may also want to, in the context of your problem and what you seek, to
1.
(1) set Settings -> Privacy and Security -> Browser Privacy to Strict or 
Custom, and

(2) view and consider the Cookies and Site Data settings, and,
(3) the History settings there, and,
(4) in Security, make sure that each of
Block dangerous and deceptive content
Block dangerous downloads
Warn you about unwanted and uncommon software,
is selected

and
2. In Tools -> Add-ons and Themes, search for, and install Bluhell 
Firewall. If I find a URL to be blocked by that, if, and, only if, I 
sufficiently trust the URL, I then open the URL in the Pale Moon web 
browser, where I have, amongst other things, an ad-blocker installed.



..
Bret Busby
Armadale
West Australia
(UTC+0800)
..

Re: FIREFOX is killing the whole PC PART II

[Gareth Evans]

On Mon 21 Nov 2022, at 06:56, Gareth Evans  wrote:
> On Sun 20 Nov 2022, at 10:53, Schwibinger Michael  wrote:
>> Hello
>> and thank You.
>> 
>> 
>> 
>> 
>> Thank you, this did help.
>
>> Two Questions more.
>
>> How can I find by terminal all dirt which is produced by browsers (Chrome, 
>> Firefox, Midori ...)?
>> I did try something like cache, but there were no new files.
>
> I think it would be easier to clear the cache and other data (possibly 
> including history if you wish) automatically when the browsers close.  
> There are usually settings available to do that.
>
> See below.
>
>> How can I tell the browser (Firefox, Chrome and so on): Do not save any 
>> information.
>> Example:
>> I do open www.hotmail.de, sending Emails, and close hotmail.
>> No there should be no information left on the pc abour hotmail. Only the 
>> bookmark www.hotmail.de.
>
> If you mean an actual bookmark, clearing the history will not remove this.
>

> For Firefox:
>
> Settings > Privacy and Security
>
> - Delete cookies and site data when Firefox is closed
>
> - History 

Make sure "Firefox will: Use custom settings for history" is selected, to see 
further options

Re: FIREFOX is killing the whole PC PART II

[Gareth Evans]

On Sun 20 Nov 2022, at 10:53, Schwibinger Michael  wrote:
> Hello
> and thank You.
> 
> 
> 
> 
> Thank you, this did help.

> Two Questions more.

> How can I find by terminal all dirt which is produced by browsers (Chrome, 
> Firefox, Midori ...)?
> I did try something like cache, but there were no new files.

I think it would be easier to clear the cache and other data (possibly 
including history if you wish) automatically when the browsers close.  There 
are usually settings available to do that.

See below.

> How can I tell the browser (Firefox, Chrome and so on): Do not save any 
> information.
> Example:
> I do open www.hotmail.de, sending Emails, and close hotmail.
> No there should be no information left on the pc abour hotmail. Only the 
> bookmark www.hotmail.de.

If you mean an actual bookmark, clearing the history will not remove this.

For Firefox:

Settings > Privacy and Security

- Delete cookies and site data when Firefox is closed

- History 
-- Clear history when Firefox closes [Settings...]

There are options for what to clear if you click the "settings" button, such as 

- browsing history
- cookies
- cache

So there seem to be two ways to clear cookies and site data when closing 
Firefox, but I'm not sure if the options under History > Settings include all 
the "site data" removed by the other setting.

Best wishes,
Gareth



> 
> 
> Thank you.
> 
> 
> Reards,
> Sophie
> 
> 
> 
> *Von:* Gareth Evans 
> *Gesendet:* Samstag, 19. November 2022 14:12
> *An:* debian-user@lists.debian.org 
> *Betreff:* Re: FIREFOX is killing the whole PC 
>  
> On Sat 19 Nov 2022, at 13:14, DdB  
> wrote:
> > Am 19.11.2022 um 10:34 schrieb Schwibinger Michael:
> >> Hello
> >> 
> >> Any idea?
> >> 
> >> What did happen?
> >> FF did open a page with bad PC,
> >> so it needs 5 minutes to open it.
> >> We killed the tab.
> >> When we now try to open FF
> >> whole PC is blocked.
> >> How can we clean FF
> >> because bad page is in it.
> >> 
> >> Regards
> >> Sophie
> >> 
> 
> > Did you try to start it from the commandline with the option safe-mode?
> >
> > firefox --safe-mode
> 
> If the idea is to prevent previous tabs from opening on startup, that only 
> works for me if firefox is already running when I run 
> 
> firefox --safe-mode
> 
> ...which may not be possible for Sophie.
> 
> Removing the line:
> 
> user_pref("browser.startup.page", 3);
> 
> from
> 
> /home/username/.mozilla/firefox/XXX.default-esr/prefs.js
> 
> has the desired effect (where "XXX" is the appropriate string of letters and 
> numbers).
> 
> There may be more than one such profile directory, in which case, if other 
> users don't rely on tabs being restored, then remove that line from all the 
> 
> XXX.whatever/prefs.js 
> 
> files you can find.
> 
> It may also be necessary to add the line
> 
> user_pref("browser.sessionstore.resume_from_crash", false);
> 
> I don't know if the order of lines matters.  In my prefs.js, this appears in 
> the sequence
> 
> user_pref("browser.search.region", "GB");
> user_pref("browser.search.widget.inNavBar", true);
> user_pref("browser.sessionstore.resume_from_crash", false);
> 
> when added from about:config, but the 2nd line is non-default as well as the 
> 3rd, and these are only present if added manually or set in settings or 
> about:config, as appropriate.
> 
> Hope that helps
> Gareth
> 
> 
> 

Re: AW: FIREFOX is killing the whole PC Part III

[Curt]

On 2022-11-20, Schwibinger Michael  wrote:
>
> To avoid problems by surfing
> I tried
> nice.
> No good enough.
>
> I did try
>
> nice -n 19 chromium-browser
>  cpulimit -e chrome -l 30
>
> But this also did not work,
> cause URLS do open other URLs.
>
> I found this.
>
> 2 Questions:
>
> What does it do?
>
> Why does it not work.
>
>
> # Find and limit all child processes of all browsers.
> for name in firefox firefox-esr chromium chrome
> do
> for ppid in $(pgrep "$name")
> do
> cpulimit --pid="$ppid" --limit"$LIMIT" &
> for pid in "$ppid" $(pgrep --parent "$ppid")
> do
> cpulimit --pid="$pid" --limit"$LIMIT" &
> done
> done
> done
>
> Regards Sophie

I suppose it does what it says in the comment at the front, and fails to
work because you need to define $LIMIT beforehand.

  -l, --limit=N
 percentage  of  CPU allowed from 1 up. Usually 1 - 100,
 but can be higher on multi-core CPUs. (mandatory)


  # cpulimit -l 20 firefox
 Launch Firefox web browser and limit its CPU usage to
 20%

AW: FIREFOX is killing the whole PC Part III

[Schwibinger Michael]

To avoid problems by surfing
I tried
nice.
No good enough.

I did try

nice -n 19 chromium-browser
 cpulimit -e chrome -l 30

But this also did not work,
cause URLS do open other URLs.

I found this.

2 Questions:

What does it do?

Why does it not work.


# Find and limit all child processes of all browsers.
for name in firefox firefox-esr chromium chrome
do
for ppid in $(pgrep "$name")
do
cpulimit --pid="$ppid" --limit="$LIMIT" &
for pid in "$ppid" $(pgrep --parent "$ppid")
do
cpulimit --pid="$pid" --limit="$LIMIT" &
done
done
done

Regards Sophie



Von: DdB 
Gesendet: Samstag, 19. November 2022 16:32
An: Schwibinger Michael 
Cc: debian-user 
Betreff: Re: FIREFOX is killing the whole PC

Am 19.11.2022 um 15:04 schrieb Schwibinger Michael:
> Hello
> Thank You.
> I tried
> also with CPU Limit
> bute it did catch the whole CPU:
>
> Where can I delete by terminal the whole cache?
>
> Regards
> Sophie

Hello Sophie!

I suggest you to relax a bit, otherwise your aggressive attempts to
remedy a sim0le problem might cause further havor that can be difficult
to fix later.

You situation is not dramatic, and erasing the cache is possible, but
not meaningful.

Myself, i am using Firefox differently from you, it never reopens
anything due to my settings. But i just tried it and saw, that safe-mode
was in fact not helping. (Sorry for that!)

And i found a proper description of how to fix the problem here
<https://support.mozilla.org/en-US/questions/870805>

I hope your english will be good enough to understand the approach, and
your computer skill will suffice to execute this remedy.

Otherwise ask again on the list and people will be able to explain it
differently.

best regards, DdB

Re: FIREFOX is killing the whole PC Part III

[DdB]

Am 20.11.2022 um 12:06 schrieb Schwibinger Michael:
> 
> 2 Questions:
> 
> What does it do?

The script, that you included, seems to search for a couple of browser
processes to limit their usage of CPU resources.

I do not think, this would be such a great idea.

In order to avoid, that a browser changes your system in any way, you
could do, what i do:

I did locate the places, the browser uses (not just as cache, but also
for storing defaults, history, and such). Then i use a tmpfs to create
an overlay filesystem and allow the browser to change those filesystems
only temporarily.
works as intended, but created problems, if you WANT to change something
(like f.i. download a file).

But this method is a bit difficult to implement for someone, who is
incomfortable with commandline and scripts.

AW: FIREFOX is killing the whole PC PART II

[Schwibinger Michael]

Hello
and thank You.




Thank you, this did help.

Two Questions more.
1
How can I find by terminal all dirt which is produced by browsers (Chrome, 
Firefox, Midori ...)?
I did try something like cache, but there were no new files.

Second Question
How can I tell the browser (Firefox, Chrome and so on): Do not save any 
information.
Example:
I do open www.hotmail.de, sending Emails, and close hotmail.
No there should be no information left on the pc abour hotmail. Only the 
bookmark www.hotmail.de.


Thank you.


Reards,
Sophie



Von: Gareth Evans 
Gesendet: Samstag, 19. November 2022 14:12
An: debian-user@lists.debian.org 
Betreff: Re: FIREFOX is killing the whole PC

On Sat 19 Nov 2022, at 13:14, DdB  
wrote:
> Am 19.11.2022 um 10:34 schrieb Schwibinger Michael:
>> Hello
>>
>> Any idea?
>>
>> What did happen?
>> FF did open a page with bad PC,
>> so it needs 5 minutes to open it.
>> We killed the tab.
>> When we now try to open FF
>> whole PC is blocked.
>> How can we clean FF
>> because bad page is in it.
>>
>> Regards
>> Sophie
>>

> Did you try to start it from the commandline with the option safe-mode?
>
> firefox --safe-mode

If the idea is to prevent previous tabs from opening on startup, that only 
works for me if firefox is already running when I run

firefox --safe-mode

...which may not be possible for Sophie.

Removing the line:

user_pref("browser.startup.page", 3);

from

/home/username/.mozilla/firefox/XXX.default-esr/prefs.js

has the desired effect (where "XXX" is the appropriate string of letters and 
numbers).

There may be more than one such profile directory, in which case, if other 
users don't rely on tabs being restored, then remove that line from all the

XXX.whatever/prefs.js

files you can find.

It may also be necessary to add the line

user_pref("browser.sessionstore.resume_from_crash", false);

I don't know if the order of lines matters.  In my prefs.js, this appears in 
the sequence

user_pref("browser.search.region", "GB");
user_pref("browser.search.widget.inNavBar", true);
user_pref("browser.sessionstore.resume_from_crash", false);

when added from about:config, but the 2nd line is non-default as well as the 
3rd, and these are only present if added manually or set in settings or 
about:config, as appropriate.

Hope that helps
Gareth

Re: FIREFOX is killing the whole PC

[DdB]

Am 19.11.2022 um 15:04 schrieb Schwibinger Michael:
> Hello
> Thank You.
> I tried
> also with CPU Limit
> bute it did catch the whole CPU:
> 
> Where can I delete by terminal the whole cache?
> 
> Regards
> Sophie

Hello Sophie!

I suggest you to relax a bit, otherwise your aggressive attempts to
remedy a sim0le problem might cause further havor that can be difficult
to fix later.

You situation is not dramatic, and erasing the cache is possible, but
not meaningful.

Myself, i am using Firefox differently from you, it never reopens
anything due to my settings. But i just tried it and saw, that safe-mode
was in fact not helping. (Sorry for that!)

And i found a proper description of how to fix the problem here


I hope your english will be good enough to understand the approach, and
your computer skill will suffice to execute this remedy.

Otherwise ask again on the list and people will be able to explain it
differently.

best regards, DdB

Re: FIREFOX is killing the whole PC

[Gareth Evans]

> On 19 Nov 2022, at 15:44, Gareth Evans  wrote:
> 
> 
> 
>>> On 19 Nov 2022, at 15:25, Andrew M.A. Cater  wrote:
>>> 
>>> On Sat, Nov 19, 2022 at 09:34:40AM +, Schwibinger Michael wrote:
>>> Hello
>>> 
>>> Any idea?
>>> 
>>> What did happen?
>>> FF did open a page with bad PC,
>>> so it needs 5 minutes to open it.
>>> We killed the tab.
>>> When we now try to open FF
>>> whole PC is blocked.
>>> How can we clean FF
>>> because bad page is in it.
>>> 
>>> Regards
>>> Sophie
>>> 
>> 
>> Hi Sophie,
>> 
> 
>> If you can start the machine and leave it for ten minutes to let Firefox run
>> you may find that you can clear the cache and history. 
> 
> Hi Andy,
> 
> How could history be related?
> 

> Might it be worth just deleting
> 
> /home/username/.cache/mozilla/firefox
> 

(And switching off restoring previous tabs)

> ?
> 
> Thanks
> Gareth

Re: FIREFOX is killing the whole PC

[Gareth Evans]

> On 19 Nov 2022, at 15:25, Andrew M.A. Cater  wrote:
> 
> On Sat, Nov 19, 2022 at 09:34:40AM +, Schwibinger Michael wrote:
>> Hello
>> 
>> Any idea?
>> 
>> What did happen?
>> FF did open a page with bad PC,
>> so it needs 5 minutes to open it.
>> We killed the tab.
>> When we now try to open FF
>> whole PC is blocked.
>> How can we clean FF
>> because bad page is in it.
>> 
>> Regards
>> Sophie
>> 
> 
> Hi Sophie,
> 

> If you can start the machine and leave it for ten minutes to let Firefox run
> you may find that you can clear the cache and history. 

Hi Andy,

How could history be related?

Might it be worth just deleting

/home/username/.cache/mozilla/firefox

?

Thanks
Gareth

Re: FIREFOX is killing the whole PC

[Andrew M.A. Cater]

On Sat, Nov 19, 2022 at 09:34:40AM +, Schwibinger Michael wrote:
> Hello
> 
> Any idea?
> 
> What did happen?
> FF did open a page with bad PC,
> so it needs 5 minutes to open it.
> We killed the tab.
> When we now try to open FF
> whole PC is blocked.
> How can we clean FF
> because bad page is in it.
> 
> Regards
> Sophie
>

Hi Sophie,

If you can start the machine and leave it for ten minutes to let Firefox run
you may find that you can clear the cache and history. You may also want
to disable Firefox from opening windows that were open when it crashed so
that it does not continue to open problematic sites.

With every good wish, as ever,

Andy Cater

Re: FIREFOX is killing the whole PC

[Curt]

On 2022-11-19, Bret Busby  wrote:
> On 19/11/2022 17:34, Schwibinger Michael wrote:
>> Hello
>> 
>> Any idea?
>> 
>> What did happen?
>> FF did open a page with bad PC,
>> so it needs 5 minutes to open it.
>> We killed the tab.
>> When we now try to open FF
>> whole PC is blocked.
>> How can we clean FF
>> because bad page is in it.
>> 
>> Regards
>> Sophie
>> 
> Why is the person using a bad PC?
>
> If the PC is bad, surely, the simple solution is to get rid of the PC, 
> and use a decent PC.

I don't think Sophie is a native English speaker and by "bad" she might
have meant any number of things bar, IMHO, the inference behind
your simple solution.

> If the PC is bad, that may be the source of the problem.
>
> ..
> Bret Busby
> Armadale
> West Australia
> (UTC+0800)
> ..
>
>


-- 

Re: FIREFOX is killing the whole PC

[Bret Busby]

On 19/11/2022 17:34, Schwibinger Michael wrote:

Hello

Any idea?

What did happen?
FF did open a page with bad PC,
so it needs 5 minutes to open it.
We killed the tab.
When we now try to open FF
whole PC is blocked.
How can we clean FF
because bad page is in it.

Regards
Sophie


Why is the person using a bad PC?

If the PC is bad, surely, the simple solution is to get rid of the PC, 
and use a decent PC.


If the PC is bad, that may be the source of the problem.

..
Bret Busby
Armadale
West Australia
(UTC+0800)
..

Re: FIREFOX is killing the whole PC

[Gareth Evans]

On Sat 19 Nov 2022, at 13:14, DdB  
wrote:
> Am 19.11.2022 um 10:34 schrieb Schwibinger Michael:
>> Hello
>> 
>> Any idea?
>> 
>> What did happen?
>> FF did open a page with bad PC,
>> so it needs 5 minutes to open it.
>> We killed the tab.
>> When we now try to open FF
>> whole PC is blocked.
>> How can we clean FF
>> because bad page is in it.
>> 
>> Regards
>> Sophie
>> 

> Did you try to start it from the commandline with the option safe-mode?
>
> firefox --safe-mode

If the idea is to prevent previous tabs from opening on startup, that only 
works for me if firefox is already running when I run 

firefox --safe-mode

...which may not be possible for Sophie.

Removing the line:

user_pref("browser.startup.page", 3);

from

/home/username/.mozilla/firefox/XXX.default-esr/prefs.js

has the desired effect (where "XXX" is the appropriate string of letters and 
numbers).

There may be more than one such profile directory, in which case, if other 
users don't rely on tabs being restored, then remove that line from all the 

XXX.whatever/prefs.js 

files you can find.

It may also be necessary to add the line

user_pref("browser.sessionstore.resume_from_crash", false);

I don't know if the order of lines matters.  In my prefs.js, this appears in 
the sequence

user_pref("browser.search.region", "GB");
user_pref("browser.search.widget.inNavBar", true);
user_pref("browser.sessionstore.resume_from_crash", false);

when added from about:config, but the 2nd line is non-default as well as the 
3rd, and these are only present if added manually or set in settings or 
about:config, as appropriate.

Hope that helps
Gareth

Re: FIREFOX is killing the whole PC

[DdB]

Am 19.11.2022 um 10:34 schrieb Schwibinger Michael:
> Hello
> 
> Any idea?
> 
> What did happen?
> FF did open a page with bad PC,
> so it needs 5 minutes to open it.
> We killed the tab.
> When we now try to open FF
> whole PC is blocked.
> How can we clean FF
> because bad page is in it.
> 
> Regards
> Sophie
> 
Did you try to start it from the commandline with the option safe-mode?

> firefox --safe-mode

FIREFOX is killing the whole PC

[Schwibinger Michael]

Hello

Any idea?

What did happen?
FF did open a page with bad PC,
so it needs 5 minutes to open it.
We killed the tab.
When we now try to open FF
whole PC is blocked.
How can we clean FF
because bad page is in it.

Regards
Sophie