public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Firefox crashes on some www-pages on a newer Gentoo system
Date: Sun, 16 Sep 2018 08:50:11 +0100	[thread overview]
Message-ID: <3443910.MWza0qdKvM@dell_xps> (raw)
In-Reply-To: <CA+t6X7f-FdRTHnQbCBOWkWFUYT0+PWBJ_CNN71HRZ382r+3wOA@mail.gmail.com>

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

On Sunday, 16 September 2018 08:19:30 BST gevisz wrote:
> пт, 7 сент. 2018 г. в 19:05, Mick <michaelkintzios@gmail.com>:
> > On Friday, 7 September 2018 16:32:40 BST gevisz wrote:
> > 
> > Something else I came across causing FF crashes here, was a bug with
> > profile- sync-daemon (recent thread of mine refers).  I don't know if you
> > use psd, but I wasn't aware of this psd bug when you posted about your
> > problems.  I only mention it now as another thing to check next time you
> > have FF crashing on you.
> 
> Thank you for additional information.
> 
> I have read in this mailing list (may be it was your thread) that using
> profiles in firefox is another source of crashes. So, I do not use
> profiles, and now hope that it means that I do not use psd as well. :)

Ah! No, they are too different things.

I have not read anywhere that the use of multiple user profiles causes FF to 
crash.  Perhaps some addons may do.

The use of psd on the other hand is a useful package, minimising the writing 
cycles of the browser's cache to disk.  If your PC is running on SDD or hybrid 
disks and has enough RAM, then a profile-sync-daemon (when it is not buggy) 
should be a good thing.
-- 
Regards,
Mick

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

  reply	other threads:[~2018-09-16  7:50 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-27  8:16 [gentoo-user] Firefox crashes on some www-pages on a newer Gentoo system gevisz
2018-07-27  9:44 ` Mick
2018-07-27 10:44   ` gevisz
2018-07-27 10:57     ` Mick
2018-07-27 11:13       ` gevisz
2018-07-27 12:44         ` gevisz
2018-07-27 13:00           ` gevisz
2018-07-27 15:29             ` Mick
2018-07-27 18:49               ` gevisz
2018-07-27 20:02                 ` Mick
2018-07-28 12:24                   ` gevisz
2018-07-29 20:48                     ` gevisz
2018-07-31 23:41                       ` Adam Carter
2018-08-01  9:33                         ` gevisz
2018-08-02  0:16                           ` Adam Carter
2018-08-02  5:15                             ` gevisz
2018-09-07 15:32               ` gevisz
2018-09-07 16:05                 ` Mick
2018-09-16  7:19                   ` gevisz
2018-09-16  7:50                     ` Mick [this message]
2018-09-16  8:08                       ` Dale
2018-09-16 11:32                         ` gevisz
2018-09-16 11:47                           ` Mick
2018-09-16 11:51                           ` Dale
2018-09-16 11:25                       ` gevisz

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=3443910.MWza0qdKvM@dell_xps \
    --to=michaelkintzios@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